a month ago
Could you investigate a persistent 502 Bad Gateway on the public Railway domain for the second project? Both backend and frontend services are deployed successfully, show healthy internal status, and listen on the expected ports, but the public domain still fails. Please verify whether this is an edge proxy, routing, or networking issue on the project.
Pinned Solution
a month ago
That's what I just said... to make sure the port of the application and the URL is the same...
3 Replies
Status changed to Open Railway • 30 days ago
a month ago
Make sure the port your application is listening to is the same port your URL is mapped to.
0x5b62656e5d
Make sure the port your application is listening to is the same port your URL is mapped to.
a month ago
I verified that the application is healthy, but I would like you to confirm whether the public domain target port matches the actual listening port of the service. A port mismatch between the app and the Railway public URL mapping may be causing the 502 response.
Status changed to Awaiting User Response Railway • 30 days ago
a month ago
That's what I just said... to make sure the port of the application and the URL is the same...
Status changed to Awaiting Railway Response Railway • 30 days ago
Status changed to Solved ray-chen • 29 days ago