a month ago
Hi Railway team,
I’m facing an issue where my deployed Railway backend service is healthy and running correctly, but the generated public domain is not resolving publicly.
Project details:
- Service status: Active
- Deployment successful
- App is listening successfully
- Prisma/Postgres connected successfully
- Public networking enabled
- Correct port attached (8000)
Observed issue:
-
Browser shows:
DNS_PROBE_FINISHED_NXDOMAIN
-
nslookup returns:
REFUSED
-
HTTP logs remain completely empty, meaning requests never reach the service
What I already tested:
- Regenerated public domains
- Renamed service
- Fresh Railway project
- Redeployed multiple times
- Removed manual PORT variable
- Verified app.listen on 0.0.0.0
- Different devices/networks
- DNS changes (Google/Cloudflare DNS)
Deployment logs confirm:
- Server starts successfully
- app.listen callback triggers
- Prisma connects successfully
- Container is healthy
Network Flow Logs also show successful internal networking and Postgres connectivity.
This appears to be a Railway public DNS / edge routing issue for the generated up.railway.app domain.
Could you please investigate the DNS/public routing for this deployment?
Thank you.
1 Replies
a month ago
Your domain riverpe-api-production.up.railway.app is resolving correctly from the public internet to the expected IP address, and your latest deployment shows a successful status. The DNS_PROBE_FINISHED_NXDOMAIN error is originating from your local network or DNS resolver, not from our side. Try flushing your local DNS cache (e.g., ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS), and if the issue persists, try a completely different network (e.g., mobile hotspot) to rule out ISP-level DNS caching.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved swarajriverpe • about 1 month ago