# The train has not arrived at the station. Please check your [network settings](https://docs.railway.com/guides/public-networking#railway-provided-domain) to confirm that your domain has provisioned. If you are a visitor, please let the owner know you're stuck at the station.

I had this problem as well, but it seemed to fix itself when I enabled Private Networking for the environment and redeployed the service. \--- Here's what I remember: * Before, the server logs would say it's listening on port 8080, but railway would display the same error message when i tried to access it from the service's domain. * Redeploying alone did not work for me * I deployed the same repo as a new service to see if it was reproducible, and this happened to enable private networking for the environment. * Clicking on my old service that was getting the Not Found error showed "unable to get private networking endpoint" (previously showed "enable private networking" button) * I redeployed the existing service that was broken (this is the only change I made to the service after private networking got turned on automatically) * It got its own private `.railway.internal` domain created automatically * I was able to access the service from its domain again after the redeploy. I suspect the issue may be related to one of the recent outages since the HTTP logs showed a gap in traffic starting around this time: * *

Not Found - Railway Central Station

Not Found

kisskrisztina

HOBBYOP

2 months ago

The train has not arrived at the station.

Please check your network settings to confirm that your domain has provisioned.

If you are a visitor, please let the owner know you're stuck at the station.

Solved$10 Bounty

Pinned Solution

awesome-e

HOBBY

2 months ago

I had this problem as well, but it seemed to fix itself when I enabled Private Networking for the environment and redeployed the service.

---

Here's what I remember:

Before, the server logs would say it's listening on port 8080, but railway would display the same error message when i tried to access it from the service's domain.
Redeploying alone did not work for me
I deployed the same repo as a new service to see if it was reproducible, and this happened to enable private networking for the environment.
Clicking on my old service that was getting the Not Found error showed "unable to get private networking endpoint" (previously showed "enable private networking" button)
I redeployed the existing service that was broken (this is the only change I made to the service after private networking got turned on automatically)
It got its own private .railway.internal domain created automatically
I was able to access the service from its domain again after the redeploy.

I suspect the issue may be related to one of the recent outages since the HTTP logs showed a gap in traffic starting around this time:

4 Replies

Status changed to Awaiting Railway Response brody • 2 months ago

0x5b62656e5d

MODERATOR

2 months ago

Make sure the route actually exists, and that the port your application is listening on is the same port your URL is mapped to.

kisskrisztina

HOBBYOP

2 months ago

Where can I watch this?

awesome-e

HOBBY

2 months ago

I had this problem as well, but it seemed to fix itself when I enabled Private Networking for the environment and redeployed the service.

---

Here's what I remember:

Before, the server logs would say it's listening on port 8080, but railway would display the same error message when i tried to access it from the service's domain.
Redeploying alone did not work for me
I deployed the same repo as a new service to see if it was reproducible, and this happened to enable private networking for the environment.
Clicking on my old service that was getting the Not Found error showed "unable to get private networking endpoint" (previously showed "enable private networking" button)
I redeployed the existing service that was broken (this is the only change I made to the service after private networking got turned on automatically)
It got its own private .railway.internal domain created automatically
I was able to access the service from its domain again after the redeploy.

I suspect the issue may be related to one of the recent outages since the HTTP logs showed a gap in traffic starting around this time:

kisskrisztina

HOBBYOP

2 months ago

Thank you, I managed to solve it.

Status changed to Solved sam-a • 2 months ago

Welcome!