Help with Railway URL Not Working (Hobby Plan)

snootypebbles

HOBBYOP

a month ago

I’m having trouble with my app’s URL, https://fairsprint-server-production.up.railway.app/

, which isn’t working as expected. It’s showing the error DNS_PROBE_FINISHED_NXDOMAIN, indicating that the domain is not resolving.

Here’s a brief overview of what I’ve done:

The app is deployed and running with the status "Starting Container" in the logs.

The logs show the following output after starting:

npm warn config production Use --omit=dev instead.

> server@1.0.0 start

> node server.js

Server + WebSocket running at http://localhost:8080

Environment: production

Please Help

Solved$10 Bounty

6 Replies

Railway

BOT

a month 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!

brody

EMPLOYEE

a month ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody • about 1 month ago

ari-party

PROTop 10% Contributor

a month ago

Is it still failing? Your app resolves on my end

snootypebbles

HOBBYOP

a month ago

Its not working, its still failing, This site can’t be reached

Check if there is a typo in fairsprint-server-production.up.railway.app.

DNS_PROBE_FINISHED_NXDOMAIN

snootypebbles

HOBBYOP

a month ago

Hi railway team, Can someone please help me here?

bramsuurdje

HOBBY

a month ago

I have the feeling this is a local DNS issue since i can reach your service. try the following depending on your system. after this try doing nslookup fairsprint-server-production.up.railway.app and let me know what the output is if it didnt fix the problem

Windows: Open Command Prompt as administrator and run ipconfig /flushdns.

macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

Linux: The command varies by distribution. Common commands include sudo systemd-resolve --flush-caches or sudo /etc/init.d/nscd restart.

snootypebbles

HOBBYOP

a month ago

Thanks man It worked, my old DNS was just blocking or caching garbage

Status changed to Solved noahd • about 1 month ago