After a successful application deployment, if there’s an issue within the application’s code or configuration, you may see the following error when you try to go to your application’s URL:

503 Service Temporarily Unavailable

If you cannot identify the issue, check the following.

Workspace Path

If your application uses a buildpack and an Apache web server, an incorrect workspace path in your Apache configuration can cause a 503 error. The application logs may show an error similar to the following:

python: can't open file '/workspace/': [Errno 2] No such file or directory

This error shows that the command the buildpack is trying to run doesn’t exist. Update your Apache configuration to use /workspace/web/ (instead of  /workspace/ or similar) to resolve this issue.

Note: This issue may also present as an oom-killed error in the runtime logs (but it isn’t the only possible cause of an oom-killed error).

If the error persists after checking and fixing any configuration issues, follow our Failed Rollout troubleshooting guide. If the error remains beyond those steps, contact our Support team.

Related Documentation