2 months ago
I'm unable to reach OpenAI's API from my Railway deployment. Here are the details:
Environment:
- Project: intuitive-illumination
- Service: @cia/runner
- Region: us-east4-eqdc4a
Issue: Outbound HTTPS connections to OpenAI hang indefinitely and never complete the TLS handshake.
Diagnostics:
curl https://api.openai.com– hangs (no response, times out)curl https://google.com– works fine (returns 301)nslookup api.openai.com– resolves correctly to 172.66.0.243 and 162.159.140.245curl -v https://openai.com– hangs at "Trying 172.64.154.211:443..."- IPv6 egress: disabled (
ipv6EgressEnabled: false) - Container capabilities: ping blocked (Operation not permitted)
What I've tried:
- Disabled IPv6 egress
- Redeployed the service
- Verified DNS resolution works
- Tested with different OpenAI endpoints
What I need: Please check if there's an egress routing issue, firewall rule, or known connectivity problem between Railway's us-east4-eqdc4a region and OpenAI's Cloudflare CDN IPs.
2 Replies
2 months 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 • 2 months ago
2 months ago
The issue is with Railway, it will be fixed soon https://status.railway.com/cmmrjwx4x0ltkf6zwi526b038
2 months ago
thank you for responding! great time i picked to give "this railway" thing a try 😂
it is marked as resolved however the same symptoms still persist in the container I am testing in
Update: now curl http(s)://google.com/ hangs as well