Known problems and fixes

1. Find the passwords the database was created with. Look in the .env that was in use when the volume was created, or in a copy under backups/update-*/ in the install folder. This command shows the date:

docker volume inspect atglance_db-data --format '{{.CreatedAt}}'

2. Test a candidate password. 1 means it is correct, ERROR 1045 means it is not:

docker exec -e P='<password>' ce-atglance-db sh -c 'MYSQL_PWD="$P" mysql -uatglance -P23306 -h127.0.0.1 -e "select 1"'

3. Back up the install's .env. Then set DB_PASSWORD and DB_ROOT_PASSWORD to the working values. Leave REDIS_PASSWORD unchanged. On Windows, edit C:\ProgramData\AtGlance.env from an Administrator PowerShell.

4. Re-create the containers:

docker compose up -d --force-recreate

Prevention: If you run a development copy on the same machine, start it under its own project name so it does not share the install's database:

docker compose -p atglance-dev -f docker-compose.yml -f docker-compose.dev.yml up -d --build

Cause: the proxy does not pass the real host name and HTTPS to the console, so the page links its styles to http://localhost or http://127.0.0.1:8000, which the browser cannot load.

Check which address the page uses.

Linux:

curl -s https://<your-domain>/ | grep -o 'href="[^"]*atglance.css[^"]*"'

Windows (PowerShell):

(Invoke-WebRequest https://<your-domain>/ -UseBasicParsing).Content | Select-String 'href="[^"]*atglance.css[^"]*"' | ForEach-Object { $_.Matches.Value }

It should start with https://<your-domain>/. If it shows localhost, 127.0.0.1 or http://, follow these steps.

1. Pass the host name and HTTPS through the proxy

nginx: use this location block in the site config, then run nginx -t && nginx -s reload.

location / {
    proxy_pass http://127.0.0.1:8000;
    proxy_set_header Host              $host;
    proxy_set_header X-Forwarded-Host  $host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-Port  $server_port;
    proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header X-Real-IP         $remote_addr;
}

Cpanel/aaPanel/CloudPanel: open the site, Reverse proxy, then edit the proxy for /:

• Reverse proxy tab: keep the target http://127.0.0.1:8000 and set Send Host to $host. Save.
• Config tab: paste the three lines below and save. Leave out X-Forwarded-For; aaPanel already sets it.

proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;

Apache: in the HTTPS virtual host, next to ProxyPass / http://127.0.0.1:8000/, add:

ProxyPreserveHost On
RequestHeader set X-Forwarded-Proto "https"

2. Let the console trust the proxy

The proxy reaches the console from the Docker network, which it does not trust by default. Run on the server.

Linux:

docker exec ce-atglance-app sh -c 'echo "ATGLANCE_TRUSTED_PROXIES=127.0.0.1,::1,172.16.0.0/12" >> /app/storage/.env'
cd /opt/atglance && docker compose restart app worker scheduler

Windows (PowerShell):

docker exec ce-atglance-app sh -c 'echo "ATGLANCE_TRUSTED_PROXIES=127.0.0.1,::1,172.16.0.0/12" >> /app/storage/.env'
cd C:\ProgramData\AtGlance; docker compose restart app worker scheduler

3. Set the domain in the console

Log in on http://<server-ip>:8000 as the super admin:

• Site Settings → Plugins: turn on Custom Domain & HTTPS.
• Site → Access URL: enter your domain, without http:// and without a port.
• HTTPS: choose Handled by my platform, because your proxy holds the certificate. Save.

4. Check again

Run the check command again. It should now show https://<your-domain>/css/atglance.css. Reload the page with Ctrl+F5.

Servers running the atglance CLI still connect on port 8002 of the same host. Keep that port open; the domain only fronts the web console.