24 days ago
Hi Railway team,
My service (instagram-bot) has been returning ECONNREFUSED on all public domains since your May 20 incident, even though the service itself is running fine.
What I've tried:
Restarted the service multiple times
Regenerated the public domain twice (ef01 → b993)
Added a custom domain (api.codeforgeai.app) — DNS verified green but SSL not provisioning
Service logs show healthy startup: DB connected, server running on port 8080
The problem:
Service logs show it's running perfectly, but no external traffic reaches it. The public networking appears broken at the proxy/routing layer.
Service details:
Service name: instagram-bot
Domain: instagram-bot-production-b993.up.railway.app
Custom domain attempted: api.codeforgeai.app
Port: 8080
Plan: Pro
Could you please restore the public networking/proxy connection for this service?
Thanks
Bhavesh Shahani
Pinned Solution
24 days ago
Try this first:
Go to service settings → Networking → remove the public domain completely, then re-add it (don't just regenerate — fully delete and recreate). This can force a proxy re-bind.
Make sure your port is explicitly hardcoded as 8080 in Railway settings, not just relying on the PORT env var.
6 Replies
24 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 • 24 days ago
24 days ago
Try this first:
Go to service settings → Networking → remove the public domain completely, then re-add it (don't just regenerate — fully delete and recreate). This can force a proxy re-bind.
Make sure your port is explicitly hardcoded as 8080 in Railway settings, not just relying on the PORT env var.
aayankali
Try this first: Go to service settings → Networking → remove the public domain completely, then re-add it (don't just regenerate — fully delete and recreate). This can force a proxy re-bind. Make sure your port is explicitly hardcoded as 8080 in Railway settings, not just relying on the PORT env var.
24 days ago
Yes now it is working
edu124
Yes now it is working
24 days ago
my pleasure
24 days ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
Status changed to Awaiting User Response Railway • 24 days ago
edu124
Yes now it is working
24 days ago
hey can u mark the bounty as solved
cheers
Status changed to Awaiting Railway Response Railway • 24 days ago
Status changed to Solved mykal • 24 days ago