10 days ago
Service: echo-web
Custom domain: echosocial.us
Error: "The train has not arrived at the station" after re-adding domain and rebuilding service
Cloudflare DNS is correctly pointing to echo-web-production-89a6.up.railway.app
This is a Railway infrastructure issue that requires their team to investigate.
5 Replies
10 days ago
The domain echosocial.us is not currently attached to any Railway service, which is why the edge returns the "train has not arrived" fallback. Your service at echo-web-production-89a6.up.railway.app is responding normally. To fix this, add echosocial.us as a custom domain on your service in its Settings, then follow the DNS verification steps Railway provides (a CNAME pointing to your .up.railway.app domain and a TXT record for ownership verification). Since you're using Cloudflare, make sure the Cloudflare proxy (orange cloud) is turned off (grey/DNS-only) for both records so Railway can verify and issue a certificate.
Status changed to Awaiting User Response Railway • 10 days ago
3 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 • 3 days ago
2 days ago
still not fixed
Status changed to Awaiting Railway Response Railway • 2 days ago
2 days ago
The custom domain is still not added to your echo-web service on Railway, which is why the error persists. Your DNS is correctly pointing at our edge, but the domain itself needs to be registered on the service: open your echo-web service's Settings, go to Networking, click "Add Custom Domain", and enter the domain. Railway will then provide the required TXT verification record to add at Cloudflare (with the proxy toggled off/grey cloud) so ownership can be verified and a certificate issued.
Status changed to Awaiting User Response Railway • 2 days ago
2 days ago
You've already added echosocial.us as a service domain on echo-web. It's in the config.
The issue isn't the domain configuration—it's the SSL certificate. Railway auto-provisions certs for custom domains, but it requires:
DNS CNAME is set up correctly at your registrar (echosocial.us → the Railway target)
DNS has fully propagated (can take up to 48 hours)
Certificate provisioning completes (can take 24 hours after DNS is ready)
The browser warning will clear once the cert is valid. Just deployed echo-web, so give it time to retry provisioning. If it still fails in a few hours, double-check your DNS CNAME record at your registrar.
Status changed to Awaiting Railway Response Railway • 2 days ago
2 days ago
Your DNS is reaching our edge correctly, but the domain is not currently registered on your echo-web service on our side. The service's networking configuration shows only the default .up.railway.app domains and no custom domain entry. This is not an SSL issue - the certificate step only begins after the domain is added inside Railway. To proceed, open your echo-web service's networking settings and add the custom domain there, then add the TXT verification record Railway provides at Cloudflare with the proxy disabled (grey cloud).
Status changed to Awaiting User Response Railway • 2 days ago