Database troubleshooting

Symptom-led checks for database Services: deploy logs, compute, credentials, public access, env references, and backups.

Written By Zoro

Last updated 3 days ago

Start with the Deployments and Logs tabs on the database Service.

Most failures show a clear error in the provisioning log.

For App or Docker Services (build failures, image pulls), use Deployment issues under Troubleshooting in the sidebar and Logs under Deployments and Operations in the sidebar.

Deploy fails or never finishes

  1. Open Deployments on the database Service and read the latest run. Copy the first error block (redact passwords).

  2. Confirm Environment compute is healthy. See Compute and worker node issues under Troubleshooting in the sidebar.

  3. Check disk and memory on the Worker Node if the log mentions resource or storage errors.

  4. Retry Deploy if the UI still offers it (after the first success, Deploy is hidden for databases; then use Restart if the engine is running but misconfigured).

Internal credentials missing or empty

  • Deploy must complete successfully at least once. Create Service alone does not provision data files or users.

  • If the Service was Stopped, start it again with the actions available in the header (behaviour matches Databases overview).

App cannot connect (connection refused, timeout, auth failed)

  1. Confirm the App and database Services are in the same Environment if you intend to use internal hostnames.

  2. Prefer Reference variables over hand-typed URLs. See Database credentials and connections and Environment variable issues under Troubleshooting in the sidebar.

  3. After changing Variables on the App Service, redeploy the app so runtime picks up new values.

  4. If the database is external to dFlow, see External database notes and verify firewall and TLS settings.

Expose, Unexpose, and Stop

  • Stop is blocked while the database is exposed. Unexpose first.

  • While Exposing or Un-exposing, wait for the queued job to finish before clicking other destructive actions.

Reference variable is grayed out

  • Public tokens require Expose on the database Service.

  • The database Service must be deployed before internal tokens populate.

Backups stuck or restore fails

See Backups and restore (internal dumps, permissions, legacy managed-project limits). For high-level UI steps, Backups under Deployments and Operations in the sidebar under Deployments and Operations matches the same tab.

Still stuck

Use Troubleshooting overview under Troubleshooting in the sidebar to pick a broader symptom page, then When to contact support under Troubleshooting in the sidebar with logs and timestamps.

Related