2 days ago
My custom domains have VALID SSL certificates and correct config, but the edge keeps returning 404 "Application not found" with header x-railway-fallback: true. The hostnames are never routed to the service.
Project ID: 7fdb2249-fbf0-4c0c-af28-59c0b9012a7c
Environment: production
Domains affected:
- www.criativoshof.com.br → service "web" (d8a2d4e1-1c35-4351-8330-13eeab9daf0c), targetPort 3000
- criativoshof.com.br → service "web", targetPort 3000
- api.criativoshof.com.br → service "api" (bab94459-3552-48d4-a101-74e79a166ee7), targetPort 8787
Verified: certificateStatus = VALID on all three; DNS PROPAGATED (currentValue == requiredValue); targetPort matches the working *.up.railway.app service domains; service is healthy (the *.up.railway.app domains return 200). I already tried redeploying, customDomainIssueCertificate, delete+recreate, and the Cloudflare proxy toggle. The x-railway-fallback persists.
This looks like an orphaned edge routing state after the domains were recreated during setup. Could you please re-register / refresh the edge routing for these hostnames?
Example request id: rcVTDej7Q6ysgUlrBhdwDg (edge: mia1)
1 Replies
2 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 days ago
2 days ago
You need to add a TXT record for _railway-verify.www.criativoshof.com.br. If you are using the API to add your custom domain, you can find it in verificationToken under status. Same for _railway-verify.criativoshof.com.br and _railway-verify.api.criativoshof.com.br.