a year ago
I'm facing an issue with my backend deployment on Railway. The project is deployed, and Railway shows it as active, but the provided public domain is not resolving. When I try to access it in the browser, I get:
ERR_NAME_NOT_RESOLVED
DNS_PROBE_FINISHED_NXDOMAIN
I've tried the following:
Ensured Public Networking is enabled.
Restarted and redeployed the backend.
Checked logs (no critical errors, server running on
process.env.PORT || 5015).Tried accessing both the public domain and the internal Railway domain.
curl -I https://news-prime-services-production.up.railway.app/gives Could not resolve host.
Is this a DNS issue on Railway's end, or is there something I might be missing? Any help would be appreciated!
Additional Info:
Backend: Node.js with Express
Logs show "Server running on port 5015"
Custom domain is not set, using Railway's default domain
1 Replies
a year ago
Hello,
That is an issue on your side with your network, your ISP has likely put you behind some kind of restrictive firewall.
Unfortunately, we cannot help with support requests unrelated to the Railway platform or product.
Please get in contact with your ISP to resolve issues with your network.
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Closed brody • about 1 year ago