Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Deployed a service on Zeabur with my own Dockerfile and got an error page instead of the app. Setting the PORT environment variable did not change anything. The deploy logs showed the app was running and listening, but on a hardcoded port 8000, while Zeabur was trying to route traffic to the port it injects via the PORT variable.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Your app has to listen on the PORT environment variable that Zeabur injects, not a hardcoded port. If your code says something like app.listen(8000), Zeabur cannot route traffic to it and you get the error page. Change it to read the variable with a fallback, for example in Node: app.listen(process.env.PORT || 8000). The reporter confirmed this fixed the deploy immediately. Source: https://github.com/zeabur/zeabur/issues/46
Shows how to fix zeabur custom Dockerfile deploy shows error page, port not exposed. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix 502 on Zeabur Docker deploy when the app uses a custom port. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes ModuleNotFoundError when deployed Prefect flows run concurrently from a custom image by upgrading to Prefect 3.2.14 or newer, where flow loading is thread-safe.