Skip to content
Railway not connecting root domain with Cloudflare DNS
scalingad
OP

a month ago

Railway not connecting root domain with Cloudflare DNS.

All DNS records are validated and working correctly, but when visiting the site, then I get this below.

Not Found

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.

Request ID:

7bzQ_4OJTt-Mr_bs8Hk9cQ

Solved

1 Reply

Railway
BOT

a month ago

Your root domain is set up correctly: it is verified, its certificate is valid, and requests reach your front-end service, which answers with a 301 redirect to the www version of the domain. The www version is not added as a custom domain on any of your services, so when the browser follows that redirect our edge has no route for it and shows the "train has not arrived" page.

To fix it, either add the www version as a custom domain on the front-end service (under the service's Settings, Networking) and create the CNAME record shown there at Cloudflare, or change your app's configuration so it serves the root domain directly instead of redirecting to www.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...