9 days ago
Hi Railway team,
My Railway-generated domain works correctly, but my custom domain:
chaen.shop
returns the Railway fallback page:
"Not Found - The train has not arrived at the station."
The application itself is healthy and the Railway-generated domain works normally.
Current configuration:
Custom domain:
chaen.shop
Target port:
8080
DNS:
CNAME chaen.shop -> vi51yn9j.up.railway.app
TXT:
_railway-verify.chaen.shop is present and Railway shows the domain as verified/green.
Cloudflare:
- I initially tested with Cloudflare Proxy enabled.
- I also disabled Cloudflare Proxy and changed the CNAME to DNS Only (gray cloud).
- The Railway 404 still occurs.
- Cloudflare SSL/TLS mode was Full while Proxy was enabled.
Railway:
- Custom domain shows green/verified.
- Target port is 8080.
- Railway-generated domain works normally.
- CDN Caching is disabled.
- No Edge Rules are configured.
Example failing Railway Request ID:
VtUbB0jUTB2R9NZcnpoFkQ
The Request ID changes on each request/refresh, but every request to chaen.shop consistently returns the same Railway fallback page:
"Not Found - The train has not arrived at the station."
The Railway-generated domain is working normally:
chaen-shop18-chaen-shop-version.up.railway.app
Could you please check whether chaen.shop has been correctly provisioned and attached to the Railway edge route/service?
If necessary, could you please re-sync the custom-domain routing on Railway's side?
Thank you.
Pinned Solution
8 days ago
The likely issue is that chaen.shop is correctly reaching the Railway service, but the application redirects it to www.chaen.shop. Since www.chaen.shop is not attached to the Railway service, Railway returns the fallback 404.
Please check the application's redirect behavior and add www.chaen.shop as a custom domain on the same Railway service, with the DNS record Railway provides. Alternatively, remove the apex-to-www redirect from the application.
2 Replies
9 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 9 days ago
8 days ago
The likely issue is that chaen.shop is correctly reaching the Railway service, but the application redirects it to www.chaen.shop. Since www.chaen.shop is not attached to the Railway service, Railway returns the fallback 404.
Please check the application's redirect behavior and add www.chaen.shop as a custom domain on the same Railway service, with the DNS record Railway provides. Alternatively, remove the apex-to-www redirect from the application.
Status changed to Solved lauragarden • 8 days ago