2 months ago
One of my services (primary-production-9024b, along with its associated worker) is unable to complete any outbound HTTP requests to any external destination tested (including unrelated domains). Connections hang indefinitely and never complete, even when an explicit timeout is configured in the application (which is ignored). I have already tried restarting the service, redeploying the service (the problem persisted identically in both cases), and increasing execution timeout settings—but nothing has resolved the issue. Inbound traffic (webhooks, scheduled triggers) continues to function normally.
4 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
can i know which kind of service is this? like a normal CRUD operation api or some heavy task ML think, i'll sound noob but have you check the cors or rate limiting? or if you have some error message or something also if you provide the tech stack that'll help understanding the problem
2 months ago
Standard API; there are no timeout errors.
2 months ago
Since it's a standard API on Railway Hobby, I'd first suspect a service-level networking/configuration issue rather than CORS. CORS doesn't affect server-side requests, and rate limiting seems unlikely if every external domain doesn't work.
Please check the service's outbound networking/egress settings first as it's the most likely issue I'd say.
If it's not that, then check: DNS resolution, private networking, and any HTTP_PROXY/HTTPS_PROXY environment variables.
2 months ago
so if its not CORS suppose, are you using SMTP in it? because if you are building a script that sends mails railway doesn't allow it in hobby plan