7 days ago
I am running a Python HTTP server on Railway.
The server listens on 0.0.0.0:8080, and the Public Networking Target Port is also 8080. A GET to /healthz from inside the container returns HTTP 200. The same endpoint through the public domain returns 502 Bad Gateway. The deployment is Active, and the startup logs show no errors.
Could you advise how to troubleshoot the connection from Railway's public proxy to the container?
1 Reply
7 days ago
The public domain on your running service is currently set to target port 8000, not 8080, so our proxy is trying to reach a port nothing is listening on, which produces the 502.
To fix it, open the service's Settings, find the domain under Public Networking, edit its target port to 8080, and save. The domain then routes to the port your server binds on 0.0.0.0:8080.
Status changed to Awaiting User Response Railway • 7 days ago
2 hours ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 hours ago