4 days ago
Request ID: 36W_i7utRFe3GjExJH0Vcg
Service: vivacious-creativity
Domain: vivacious-creativity-production-b018.up.railway.app
Port: 3000
Issue Summary:
All incoming requests are returning a 502 Bad Gateway response, although the application appears to be healthy and actively listening on port 3000.
I have another frontend app, from that app, I am trying to send request to this app & I am always getting 502.
Could you please help investigate & fix this the issue?
Thanks
Jobayer
5 Replies
4 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 4 days ago
4 days ago
I'd try changing the port the application listens to to an arbitrary number (eg, 4100) and change the port the URL is mapped to accordingly.
Also, make sure you're listening on 0.0.0.0 instead of localhost or something else.
4 days ago
A 502 Bad Gateway while the app appears healthy and listening on port 3000 usually means Railway’s edge/proxy cannot successfully communicate with the container process, even though the service is running internally.
Please verify the app is binding to 0.0.0.0:3000 (not localhost), confirm the public networking port is set to 3000, and check for runtime crashes/restarts or upstream timeouts; if all looks correct, Railway may need to inspect the edge routing for request ID 36W_i7utRFe3GjExJH0Vcg.
3 days ago
I have tried your proposed ideas, but still issue is same :( . Railway may need to inspect the edge routing for request ID 36W_i7utRFe3GjExJH0Vcg. what should I do now?
3 days ago
Are you using the PORT variable? If not, try using that instead of hardcoding the numbers.