a month ago
Project ID: 78e7e467-716d-48b7-a7a7-731489267560
Environment: production
All three services affected (api, web, operator-web)
All showing connection refused despite being online and listening
this is a staging environment intended to be used for testing. I have taken a bunch of laps with the Railway agent trying to resolve the issue. The agent suggested I open a ticket
"I can't create a support thread right now, but I need to be direct with you: This appears to be a platform-level issue at Railway that's beyond what configuration changes can fix.
All three services are:
Starting successfully
Listening on their correct ports
Showing as online/green in the dashboard
But completely unreachable from the outside (connection refused)
This systematic failure across all services simultaneously, even after:
Fixing all build and start commands
Correcting port mappings
Disabling healthchecks
Multiple redeploys"
Pinned Solution
a month ago
Also make sure that your services are binding to 0.0.0.0 not 127.0.0.1
5 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Try changing the port to an arbitrary number (eg, 4100) and change the URLs to match that as well, and redeploy.
0x5b62656e5d
Try changing the port to an arbitrary number (eg, 4100) and change the URLs to match that as well, and redeploy.
a month ago
Unfortunately this did not work. The Railway agent says this is a platform issue "This really does appear to be a platform-level issue at Railway's infrastructure level - the services are binding correctly, starting successfully, and listening on their ports, but the edge gateway still cannot route traffic to them.
At this point, the support ticket you filed is the only viable path forward. The issue is beyond what can be fixed through configuration or code changes - it's happening at Railway's networking layer between the edge and the containers."
medim
Also make sure that your services are binding to `0.0.0.0` not `127.0.0.1`
a month ago
Unfortunately this also did not work. The Railway agent created a PR which I merged. After the deploy the same bad gateway error persisted, and the same advice to rely on the support ticket.
cvonthun
Unfortunately this did not work. The Railway agent says this is a platform issue "This really does appear to be a platform-level issue at Railway's infrastructure level - the services are binding correctly, starting successfully, and listening on their ports, but the edge gateway still cannot route traffic to them. At this point, the support ticket you filed is the only viable path forward. The issue is beyond what can be fixed through configuration or code changes - it's happening at Railway's networking layer between the edge and the containers."
a month ago
This actually ended up being half of the solution...see notes attached.
Attachments
Status changed to Solved cvonthun • about 1 month ago