Custom domain routing broken again — same issue as previous ticket
willflay03-netizen
HOBBYOP

14 days ago

My custom domain refextract.com is down again with the same issue as my previous ticket. The DNS records in Namecheap are correctly configured with both CNAME records pointing to nujx9756.up.railway.app, and the domain shows as provisioned in Railway's networking settings. The Railway-generated URL loads the app fine, so the service itself is running. However, visiting refextract.com still returns the "train has not arrived at the station" error. This is the second time this has happened with no changes made on my side — the first time it was resolved on your end. Please investigate the internal routing for this domain again.

Solved

2 Replies

14 days ago

A redeploy typically resolves this, and it looks like you have done that and are no longer experiencing this issue, but we will be opening an internal investigation and will follow up here when we have more information.


Status changed to Awaiting User Response Railway 14 days ago


13 days ago

An update: we have resolved the underlying issue. You should not see this going forward.


Railway
BOT

6 days 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 6 days ago


Loading...