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
502, 503 and 504 errors from a Bahriya container usually mean no healthy replica is available or the application responds too slowly to the gateway.
2 minCommon Issues
Common issues on Bahriya and how to resolve them: stuck provisioning, restart loops, image pull errors, custom domains, secrets, and autoscaling.
4 minContainer Out of Memory
A container out of memory on Bahriya is killed and restarted — check usage against the limit, raise memory, fix leaks, or autoscale to absorb spikes.
2 minContainer Won't Start or Keeps Crash-Looping
A container that won't start or keeps crash-looping on Bahriya is almost always failing on startup — check logs, the port, and missing secrets.
2 minCustom Domain Not Resolving
A custom domain that doesn't resolve on Bahriya is nearly always a DNS record that doesn't match your DNS mode, or a change that hasn't propagated yet.
2 minDeployment Stuck in "Provisioning"
A deployment stuck in Provisioning on Bahriya usually means the image can't be pulled, the region is constrained, or the health check never passes.
2 minHealth Check Failures
Health check failures cause Bahriya to restart a container and withhold traffic — make the path return a fast, unauthenticated 2xx response to fix them.
2 minImage Cannot Be Pulled
An image pull error on Bahriya means the deployment can't fetch your image — check the reference and tag, registry credentials, and per-region deployment.
2 minTLS and Certificate Errors
TLS and certificate errors on a Bahriya custom domain usually mean the certificate has not issued yet because DNS is not in place — check the records.
2 min