Not able to access my Public URL getting: DNS_PROBE_FINISHED_NXDOMAIN

meetsoni1214

FREEOP

4 months ago

I am not able to access my Frontend and backend both via public URL which is deployed and live. I am getting the below Error:

This site can’t be reached

Check if there is a typo in social-media-frontend-production.up.railway.app.

DNS_PROBE_FINISHED_NXDOMAIN

Frontend: https://social-media-frontend-production.up.railway.app/

Backend: https://social-backend-production-71e4.up.railway.app/

Solved$10 Bounty

Pinned Solution

0x5b62656e5d

MODERATOR

4 months ago

I'm able to access the site just fine. Try clearing your local DNS cache. (Or use another incognito browser, or set the server to 1.1.1.1)

Attachments

58971.png

7 Replies

Railway

BOT

4 months ago

A DNS_PROBE_FINISHED_NXDOMAIN error means the domain does not exist in DNS, which typically occurs when no public domain has been generated for the service or the domain was removed. Please go to each service's Settings, find the Public Networking section, and verify that a Railway-provided domain is present. If not, click "Generate Domain" to create one.

Status changed to Awaiting User Response Railway • 4 months ago

Railway

A `DNS_PROBE_FINISHED_NXDOMAIN` error means the domain does not exist in DNS, which typically occurs when no public domain has been generated for the service or the domain was removed. Please go to each service's Settings, find the Public Networking section, and verify that a Railway-provided domain is present. If not, click "Generate Domain" to create one.

meetsoni1214

FREEOP

4 months ago

Already done that

Attachments

image.png

Status changed to Awaiting Railway Response Railway • 4 months ago

meetsoni1214

![](https://station-server.railway.com/attachments/att_01kjqn6pymfzyaawyjxvnjdnr1)![](https://station-server.railway.com/attachments/att_01kjqn87nffzyaawyvcp9t5tv2)Already done that

astrid

PRO

4 months ago

Can you confirm that it's still broken?

If it still is, do you see the same result when visiting the URL(s) in an incognito browser window?

0x5b62656e5d

MODERATOR

4 months ago

I'd try adding 1.1.1.1 as my browser or local machine's DNS server and see if it helps. Worst case scenario this is an ISP level block.

astrid

Can you confirm that it's still broken? If it still is, do you see the same result when visiting the URL(s) in an incognito browser window?

meetsoni1214

FREEOP

4 months ago

yes it's still broken with the same error, even in incognito browser window

0x5b62656e5d

I'd try adding `1.1.1.1` as my browser or local machine's DNS server and see if it helps. Worst case scenario this is an ISP level block.

meetsoni1214

FREEOP

4 months ago

But it is failing on my phone as well with different network :(

0x5b62656e5d

MODERATOR

4 months ago

I'm able to access the site just fine. Try clearing your local DNS cache. (Or use another incognito browser, or set the server to 1.1.1.1)

Attachments

58971.png

Status changed to Solved ray-chen • 4 months ago

Welcome!