10 months ago
curl https://developer.worldcoin.org/api/v2 locally returns successfully, while calling from inside the deployed container results in ETIMEDOUT
Pinned Solution
10 months ago
Does forcing IPv4 still time out?
Also, have you tried deploying the container in a different region?
I just spun up a bare-bones Alpine container in Singapore and curling the URL works just fine for me
8 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 ETIMEDOUT connecting to graph.facebook.com from Asia Southeast region
- 🧵 AWS SES - TCP Reset
- 🧵 Unable to reach public URL of other service during build step
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
Can you try doing curl -4 https://developer.worldcoin.org/api/v2 to see if forcing IPV4 works?
10 months ago
If it helps, I'm having a similar timeout issue with executing from inside a container, where the same call works from outside the container. Could be a Railway network issue
cwhitwell
If it helps, I'm having a similar timeout issue with executing from inside a container, where the same call works from outside the container. Could be a Railway network issue
10 months ago
Does forcing IPv4 still time out?
Also, have you tried deploying the container in a different region?
I just spun up a bare-bones Alpine container in Singapore and curling the URL works just fine for me
cwhitwell
If it helps, I'm having a similar timeout issue with executing from inside a container, where the same call works from outside the container. Could be a Railway network issue
10 months ago
Hi.
Are you in a EU region? Can you try migrating to the US eastern region for testing?
samgordon
Hi. Are you in a EU region? Can you try migrating to the US eastern region for testing?
10 months ago
Can confirm its working on US East but not EU west - is there an outage with EU?
cwhitwell
Can confirm its working on US East but not EU west - is there an outage with EU?
10 months ago
There has yet to be an official issue called, but yes, there is an issue going on in the Europe region. I would watch this thread for updates.
Status changed to Solved samgordon • 10 months ago
10 months ago
Yep, thank you very much, resolved by moving to California.
Forcing ipv4 in Europe did not help
Status changed to Awaiting Railway Response Railway • 10 months ago
Status changed to Solved szverev • 10 months ago