2 months ago
This site can’t be reached
Check if there is a typo in primary-production-0598.up.railway.app.
https://n8n-ddsky.up.railway.app/
If spelling is correct, try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
Attachments
8 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
It's working fine for me, this is likely just a caching issue - especially since this is a DNS_PROBE_FINISHED_NXDOMAIN error, usually these clear themselves within a short period of time. To verify, try accessing it again a bit later, or if you're in a hurry you can try using it on a different session/device/network.
2 months ago
If you're working with cloudflare I suggest https://developers.cloudflare.com/cache/how-to/purge-cache/ when you need some updates.
As @dev mentioned though, this was a DNS_PROBE issue so not a cache thing 
noahd
If you're working with cloudflare I suggest https://developers.cloudflare.com/cache/how-to/purge-cache/ when you need some updates. As @dev mentioned though, this was a DNS_PROBE issue so not a cache thing
2 months ago
User is using a Railway provided domain so not applicable here but good advice
2 months ago
https://n8n-ddsky.up.railway.app/
I've changed to this link, but it didn;t working for me
2 months ago
It's still working fine for me
Have you tried it on a different session/device/network?
Attachments
dev
It's still working fine for meHave you tried it on a different session/device/network?
2 months ago
Yes, now how to solve this
2 months ago
Are you still experiencing the DNS_PROBE_FINISHED_NXDOMAIN error?
The error means that your browser couldn't find the IP associated with the website from the DNS. Since it works for me- its highly likely that somewhere between you and Railway, the DNS is cached having not stored the domain. If it doesn't work on another session (session DNS cache), device (device DNS cache) or network (router&ISP DNS cache) then it could be a regional cache. If you have a VPN you can use that to see if this is the case or not.
Although I must admit I haven't seen a situation where this error has persisted this long, it usually clears up within a few hours. I suppose we also can't rule out the possibility of a block placed on Railway provided domains or IPs in your region, if it works with a VPN (pointed at a different region) then that would also hint at this being the case.
Status changed to Solved brody • 2 months ago
