Did you make sure that the port your application is listening to is the same port your URL is mapped to?

Also, check your deployment logs to make sure there aren't any other errors.

Hey, A 502 after a successful deploy usually means the app isn't binding to the port Railway expects. I'd suggest checking how your app listens for incoming connections — Railway assigns the port dynamically via an environment variable, so if your app is hardcoded to a specific port it won't line up. Also worth checking your deployment logs, they usually point you straight to the issue. Hope that helps