Self-hosting troubleshooting
Start with deploy/deploy.sh status and inspect container health. Review logs privately and redact credentials, report data, URLs and personal information before sharing diagnostics.
| Symptom | Check |
|---|---|
| Image pull is denied | Confirm the owner, repository prefix and tag, package permissions, and GHCR login for the Docker user. Registry access to an SDK package does not grant image access. |
| Server does not start | Check required production secrets, admin path and bootstrap code, .env permissions, persistent volume access and database connectivity. Do not print secret values. |
| Application or sign-in fails over HTTPS | Verify DNS, certificate validity, public URL and callback configuration, ingress profile and proxy routing. Production session cookies require HTTPS. |
| Health checks fail after a release | Check server and dashboard health and privately inspect their logs. A first release has no automatic rollback target; later automatic rollback can also fail. |
| Database connection fails | Check the URL, credentials, network access, database permissions and TLS settings. The bundled PostgreSQL container has no TLS; remote connections should use verified TLS. |
| Backup or restore fails | Check destination permissions, provider CLI and retention settings. For external PostgreSQL, use provider backups; the supplied backup script does not dump it. Verify the matching integration secret is available. |
| Rollback reports pending maintenance or revocation | Keep sharing off and all writers isolated; do not remove the pending state or manually start an older release. Follow the supported recovery procedure before restoring traffic. |
See configuration and networking and upgrades and recovery for the relevant prerequisites.