a month ago
My service is healthy and repeatedly starts successfully on port 8080, but the generated Railway public domain does not resolve.
Service: cultstore-budget-flow
Environment: production
Generated domain: cultstore-budget-flow-production.up.railway.app
Observed on May 11, 2026
Browser error: DNS_PROBE_FINISHED_BAD_CONFIG / server IP address could not be found
Evidence:
- deploy logs show “CultStore Budget Flow running at http://localhost:8080”
- local app works
- tested on mobile data too
- deleted and regenerated the Railway domain, but the new generated domain still does not resolve
2 Replies
a month ago
Your domain cultstore-budget-flow-production.up.railway.app is resolving correctly from the public internet, and your latest deployment shows as successful. The DNS_PROBE_FINISHED_BAD_CONFIG error is likely caused by a stale DNS cache on your local machine or network, possibly worsened by deleting and regenerating the domain. Try flushing your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder on macOS), then test in an incognito window or try a different DNS resolver like 1.1.1.1 or 8.8.8.8.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I already tested on mobile data as well, not just my local machine, and the generated Railway domain still does not resolve.
The service is healthy and deploy logs show:
“CultStore Budget Flow running at http://localhost:8080”
This issue was observed on May 11, 2026.
Please escalate to support because this does not appear to be a local DNS cache issue.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved anirudhpanda • about 1 month ago