a month ago
My product is down, getting a 502 error.
After several commits failed to trigger a deploy, most recent commit started a deployment, which looks successful in the logs. But my app is unreachable, I get 502 Application failed to respond.
Pinned Solution
a month ago
Is the port the public URL listening to the same port your app is listening to?
2 Replies
a month ago
Is the port the public URL listening to the same port your app is listening to?
0x5b62656e5d
Is the port the public URL listening to the same port your app is listening to?
a month ago
I just fixed it.
The public URL port was correct, but yesterday Railway suddenly started passing a PORT env ironment variable that overrides both my public listening port setting and my Dockerfile. Setting a PORT variable in the "Variables" page fixed it.
I think it's extremely unintuitive that
1) I had to set an env var
2) Railway sets one automatically that changes periodically
This weird behavior should be documented and explained in the "Public Networking" section in the settings page. I thought I was done after setting the public listening port.
Status changed to Solved brody • about 1 month ago