Troubleshooting

Common issues and specific symptoms — what they mean, and how to resolve them quickly.

9 articles

• 502, 503 and 504 Errors From Your Container

  A 5xx response served in front of your HTTP container almost always means there is no healthy replica to send the request to, or your application is too slow to respond. These errors come from the layer that sits in front of your container, so they can appear even when the container itself is up.

  2 min

• Common Issues

  This article covers common problems you may encounter when using Bahriya and how to resolve them.

  4 min

• Container Out of Memory

  A container that exceeds its memory limit is killed and restarted. Under sustained load this shows up as replicas cycling and intermittent errors. The fix is either more memory or less memory pressure in the application.

  2 min

• Container Won't Start or Keeps Crash-Looping

  Your container deploys but never reaches a healthy running state — it starts, exits, and starts again in a loop. This is almost always the application failing on startup, and the logs will tell you why.

  2 min

• Custom Domain Not Resolving

  Your custom domain doesn't load, or it resolves to the wrong place. This is nearly always a DNS record that doesn't match the DNS mode you chose, or a change that hasn't propagated yet.

  2 min

• Deployment Stuck in "Provisioning"

  A container that stays in the "Provisioning" state for more than a few minutes is usually blocked on one of three things: it can't pull the image, the region is temporarily constrained, or the health check never passes.

  2 min

• Health Check Failures

  Bahriya restarts a container whose health check fails repeatedly, and it won't serve traffic to a replica that isn't healthy. When a health check fails, the fix is to make the health check path return a 2xx response quickly and reliably.

  2 min

• Image Cannot Be Pulled

  A deployment that fails with an image pull error can't fetch the container image you referenced. The cause is either the image reference itself, or missing or misplaced registry credentials.

  2 min

• TLS and Certificate Errors

  A browser warning like "Your connection is not private" or a certificate error means a valid TLS certificate isn't being served for the hostname you're visiting. On the default hostname this is rare; on a custom domain it usually means the certificate hasn't finished provisioning because DNS isn't in place yet.

  2 min