24 days ago
I am. trying to connect custom domain. it says cname should be ktzln4j1.up.railway.app yet this link doesn't go anywhere and opens 404. My set domain is https://retv.up.railway.app/ and this one works.
This is error i am keep getting.
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:
lBxMRuCsSjq9BlLsYqdHTg
2 Replies
24 days 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 Railway • 24 days ago
24 days ago
That 404 on ktzln4j1.up.railway.app is actually expected and not a problem. Railway uses these *.up.railway.app URLs as internal routing targets for custom domains, so opening them directly in the browser often shows the “train has not arrived” 404 message. It doesn’t mean your CNAME is wrong. What matters is that your domain’s DNS is correctly pointing via CNAME to ktzln4j1.up.railway.app, with no conflicting A/AAAA records and no proxy enabled (if you’re using Cloudflare, it should be set to DNS-only). Also make sure the custom domain is attached to the same service that serves your working retv.up.railway.app. Once DNS is correct, Railway usually takes around 10–30 minutes to provision SSL and routing, so avoid repeatedly deleting and re-adding the domain. In short, ignore the 404 on the target URL and focus on DNS + proper service binding once those are correct, the custom domain should start working.