Operations and Troubleshooting

Goal

Provide common post-deployment operation commands, health checks, and troubleshooting paths.

bash

cd $INSTALL_PATH
docker compose ps
docker compose logs --tail 200 --follow
docker compose down
docker compose up -d

View application logs:

bash

tail -n 200 $INSTALL_PATH/logs/app/app.log

Update location data:

bash

bash update_geolite2.sh

Target	Command or Entry	Healthy Result
Containers	`docker compose ps`	Key services are running/up
Application health	`https://<APP_DOMAIN>/status/health`	Returns healthy status
Admin console	`/admin/login`	Login page opens
User portal	`/app/login`	Login page opens
HTTPS	Browser address bar	Certificate is valid or matches intranet policy
Replay resources	`/__replay__/...`	Enterprise resources can load

Symptom	Possible Cause	Suggested Action
Page cannot open	DNS, ports, or Caddy service issue	Check DNS, ports 80/443, firewall, and container logs
Admin cannot log in	Wrong password, init not complete, browser cache	Use installation `system` password and inspect app logs
User cannot see site	Missing group authorization, disabled site, empty category	Check group SaaS site authorization and site status
User cannot see workspace	Workspace not authorized to group	Add authorization in group workspace management
Site login fails	Account category, script, or target site policy changed	Check site config, account category config, and script match URL
Auto certificate fails	Domain does not point to public IP or ports are blocked	Confirm DNS and inbound 80/443 rules
Replay unavailable	Not a full deployment or replay storage is unreachable	Check license, deployment type, and `/__replay__/` access

Record old configurations before changing site scripts, plugins, proxies, or workspaces.
Before major upgrades, back up $INSTALL_PATH/volumes, $INSTALL_PATH/logs, and database data.
Before distributing collaboration links, open them once with a low-privilege test user.
After enabling production scripts, ask business users to verify login and key pages.