2 months ago
Railway Pro plan blocking all outbound HTTPS from n8n Docker container. Same API works in Postman.
Project ID: d37fc28a-3880-42e4-828e-47f2950c85e3
3 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 lask App – Outbound Proxy Requests Blocked / Proxy Tunnels Failing
🧵 Static Outbound IP feature not working for n8n service (ENOTFOUND error persists)
🧵 Subject: Critical Networking Issue — Outbound HTTPS Blocked on Docker App
If you find the answer from one of these, please let us know by solving the thread!
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 brody • 3 months ago
2 months ago
Have you tried manually curling the HTTP URLs via container ssh (and/or enforcing IPv4)? Chances are, it’s trying to make outbound requests via IPv6, which isn’t supported as of now.
0x5b62656e5d
Have you tried manually curling the HTTP URLs via container ssh (and/or enforcing IPv4)? Chances are, it’s trying to make outbound requests via IPv6, which isn’t supported as of now.
2 months ago
No
I just deployed my n8n on railway but I am unable to use http api node in n8n. All my requests are timing out.