Getting 502 after deployment
mohitdrumbeat
PROOP

a month ago

Hey I just deployed some changes to my app, but after deployment I'm getting 502 error when I try access my application in the browser. The logs are not showing any obvious issues though in some of the network logs I see some errors related to TCP_OVERWINDOW.

Here's my request id that I see in the browser when I try to access my application:
XDC_3zFySxe8aXmmAQeqjw

Thanks

$10 Bounty

1 Replies

Railway
BOT

a month 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 • about 1 month ago

sdpowerstrok3
FREE

a month ago

A 502 Bad Gateway after a successful deployment almost always means Railway’s proxy can’t successfully connect to your running server. In other words, the app either isn’t listening on the correct host/port combination or isn’t responding in time at all. Railway injects a PORT environment variable for your service and expects your app to bind to 0.0.0.0 on that port; if it instead listens on a fixed value (like localhost only), the proxy can’t reach it and returns 502.

Loading...