5 days ago
Hello,
I'm experiencing an issue accessing my production URL for the n8n container. When I attempt to access it via browser or ping, I consistently get a timeout. However, when I change my DNS or use a VPN, the URL becomes accessible without any problems.
Initially, I suspected a routing issue with my ISP. After several hours of troubleshooting and discussions with them, I now believe the issue might be on your end — possibly an IP block affecting my connection. Notably:
The issue only affects the n8n container URL.
I can still access other public container URLs (e.g., Postgres, Redis) without issues.
The problem is limited to a specific network. Accessing from other networks (without VPN) works fine.
No changes were made on my side before this issue began(that i know) — it started happening overnight.
I understand I might not be explaining it perfectly, but I've exhausted local troubleshooting steps and would greatly appreciate your help in investigating this further.
Thank you for your time.
2 Replies
5 days ago
Hey Siroco,
We typically don't block IPs, but can you provide a traceroute from your blocked device and non-blocked device to your production URL? That will help us rule out some potential routing issues.
Sometimes mobile ISPs do block certain routes and I've seen that cause issues in the past -- are you on a mobile phone or phone-based carrier ISP by chance?
Status changed to Awaiting User Response railway[bot] • 5 days ago
5 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 brody • 5 days ago
4 days ago
My ISP is standard fiber optic cable not mobile (altough it's not uncommon for me to see them rerouting trafic to save cost even tought is technically ilegal to do that).
The fact the i don't even see my package going to my ISP before being lost makes me thing this is not a routing issue. At the same time it is very strange it is instantly dropped. Im honestly at a loss. I have also confirmed there is nothing blocking it on my router or firewall.
Hiding IP's since thread was made public.
Tracert without VPN:
tracert primary-production-####.up.railway.app
Tracing route to trestle.proxy.rlwy.net [###.###.###.###]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms ###.###.###.###2 * * * Request timed out.
3 * * * Request timed out.
Using a VPN from the same workstation:
Tracing route to trestle.proxy.rlwy.net [###.###.###.###]
over a maximum of 30 hops:
1 14 ms 12 ms 10 ms ###.###.###.###
2 16 ms 15 ms 15 ms ###.###.###.###
3 13 ms 19 ms 14 ms lis-b1-link.ip.twelve99.net [213.248.94.124]
4 27 ms 26 ms 44 ms mad-b6-link.ip.twelve99.net [62.115.138.175]
5 65 ms 41 ms 40 ms prs-bb2-link.ip.twelve99.net [62.115.137.252]
6 * * 54 ms adm-bb2-link.ip.twelve99.net [62.115.137.4]
7 57 ms 57 ms 53 ms adm-b4-link.ip.twelve99.net [62.115.136.149]
8 61 ms 54 ms 61 ms google-ic-339903.ip.twelve99-cust.net [62.115.167.225]
9 59 ms 60 ms 57 ms 4.184.214.35.bc.googleusercontent.com [35.214.184.4]