11 days ago
Custom domain returns x-railway-fallback despite valid cert + propagated DNS
Service web, env production (selected above). Custom domain www.iriy.space returns x-railway-fallback: true 404 from the edge (ams1/cdg1), while the service domain web-production-63cbb.up.railway.app works (307). The custom domain shows certificateStatus VALID (correct CN=www.iriy.space served), DNS CNAME → vz24i7c8.up.railway.app PROPAGATED, syncStatus ACTIVE, targetPort 8080 (app listens on 0.0.0.0:8080), edgeConfig.enabled true. Already tried: re-issue cert, redeploy, set targetPort, delete+recreate the domain, updateServiceEdgeConfig, and a 12h wait. The edge never gets an upstream route for the hostname. Please re-publish/repair the edge route for www.iriy.space.
Pinned Solution
11 days ago
You need to add a TXT record for _railway-verify.www.iriy.space. If you are using the API to add your custom domain, you can find it in verificationToken under status.
1 Replies
11 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 11 days ago
11 days ago
You need to add a TXT record for _railway-verify.www.iriy.space. If you are using the API to add your custom domain, you can find it in verificationToken under status.
Status changed to Solved 0x5b62656e5d • 8 days ago