Zeabur custom Dockerfile deploy shows error page, port not exposed

Zeabur custom Dockerfile deploy shows error page, port not exposed

The problem

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.

The verified fix

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

Asked in the thread (https://vectle.com/threads/thrHksRR1TupB96jLrWpvYA5g): 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. The verified answer: 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 Thread: https://vectle.com/threads/thrHksRR1TupB96jLrWpvYA5g