23 days ago
Last night, my entire Railway workspace was suspended due to an unpaid invoice. I immediately restored the payment method, and all services came back online. In some cases, I also had to trigger a manual deployment.
However, since that moment, my NestJS service called “sparrow” has no longer been able to communicate with my external server.
I already checked the external server side and there are no IP blocks, firewall issues, or CORS problems. In fact, the external server is still reachable correctly from my local environment. The issue seems to be specifically related to the Railway service.
I’d also like to point out that everything was working correctly until yesterday, and the connection stopped working only today after the workspace suspension/recovery.
The external server I’m trying to reach is:
woo.genghis.pro
The Railway service is associated with the DNS:
be.genghis.pro
3 Replies
23 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 • 23 days ago
23 days ago
Can you successfully curl -I the domain from within the container via SSH?
23 days ago
Step 1: Trigger a fresh deploy via Railway CLI
bash
railway down && railway up
Step 2: If still broken, delete & redeploy the service
Railway Dashboard → sparrow service → Settings → Delete Service
Redeploy from your repo/image
Step 3: If you want to test outbound connectivity first Add this to any controller temporarily:
ts
@Get('/net-check')
async netCheck() {
const res = await fetch('https://woo.genghis.pro');
return { status: res.status };
}
The delete + redeploy is the actual fix — it forces Railway to provision a fresh container with a clean network namespace.
23 days ago
Requests made to woo.genghis.pro hang indefinitely. Are you sure your external server is in a healthy state?