Troubleshooting
Find the symptom, check the right log, and fix the common causes.
Start with the symptom you can see. Keep the exact error message and the time it happened - they are usually enough to find the cause.
Find your symptom
| What you see | Page |
|---|---|
| The email with your Deplo login has not arrived | Buying from hosting providers |
| You bought a server, but Deplo is missing or does not open | Buying from hosting providers |
| A question about a payment, a renewal or a refund | Buying from hosting providers |
| A build fails or a deploy is queued | Deploys and builds |
| The build passes, but the app does not answer | Deploys and builds |
| A push does not create a deploy | Deploys and builds |
| A rollback is missing or fails | Deploys and builds |
| The server is full | Deploys and builds |
| DNS, HTTPS, a 404, or a redirect is wrong | Domains and TLS |
| The panel or an app domain is unreachable | Domains and TLS |
| The server is provisioning, offline, or unhealthy | Servers and agents |
| Every deploy fails on one server | Servers and agents |
| Metrics are empty | Servers and agents |
| A container keeps restarting, is unhealthy, or is missing | Deploys and builds |
| A database will not start or an app cannot connect to it | Databases and backups |
| A backup or restore fails | Databases and backups |
| You cannot sign in, or a passkey is unusable | Sign-in and access |
| A token returns 401 or 403, or a button is missing | Sign-in and access |
Check these first
- Open the relevant log. Use the deployment's build log, the app's Logs tab, or a destination's Connection log.
- Check the server. In Settings -> Servers, refresh the server and run Check readiness if the problem involves a deploy or container.
- Separate the app from its domain. Try the generated
https://deplo-cb00710a.deplo.siteaddress. If it works, investigate DNS or the certificate. If it does not, investigate the app or server.
If it worked before, compare the last successful deploy with the failing one. The change is usually a variable, dependency, Git credential, certificate, or full disk.
Statuses people often misread
| What you see | What it means |
|---|---|
| App Error, site still works | The last deploy failed; the previous stack is still serving |
| Preview is grey | It was evicted at the preview limit; redeploy it |
| Cron skipped | It did not start because the app was stopped or another run was active |
| Cron lost | The agent could not report the result; the command may have completed |
| Server Unknown | The health reading is stale; refresh the server |
| Readiness skip | Deplo could not evaluate that check; it is not a pass |
If you still need help
Record the app, server, deploy timestamp, exact error, and the last successful deploy. Use the feature guide's Troubleshooting section for context.
Report bugs in the issue tracker; report security issues using the project's security policy.
Did this page help you?