19 days ago
Generated Railway domains for my n8n service return DNS_PROBE_FINISHED_NXDOMAIN despite correct service config and multiple domain regenerations.
Service is online and listening on port 5678.
Public Networking is mapped correctly to port 5678.
HTTP logs show zero requests reaching the service.
Issue persists across multiple generated domains:
- n8n-production-2e21b.up.railway.app
- n8n-production-3dd9.up.railway.app
- n8n-production-f2db.up.railway.app
Project ID: 5368ea7d-14db-40c5-9817-7f471182e177
Service ID: d70183fc-b904-4167-b4d7-08a96e5620f4
Please fix the public domain DNS provisioning for this service/project.
1 Replies
19 days ago
Your domain n8n-production-f2db.up.railway.app is resolving correctly from the public internet (A record: 151.101.2.15), and your service deployment shows a successful status. The NXDOMAIN error you're seeing is likely caused by a stale local DNS cache on your device or network, possibly from earlier failed lookups when the domain was first being provisioned. Flushing your local DNS cache and trying from an incognito window or different network should confirm reachability.
Status changed to Awaiting User Response Railway • 19 days ago
12 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 12 days ago