a month ago
Project: vecta-consultancy (c3c06318-92c4-42a1-a17d-49766ccc66f4)
Service: vecta-consultancy (c6f4286c-c779-4bec-b017-0591bd24bedc), env production
Custom domain: www.vectaconsultancy.com (3bc95ce3-0220-48e7-909d-80f0db9f980a)
The custom domain is registered, DNS CNAME → ezzvrizj.up.railway.app is propagated, and the Let's Encrypt cert shows VALID. But https://www.vectaconsultancy.com returns the edge fallback 404 {"status":"error","code":404,"message":"Application not found"} (x-railway-fallback: true, edge lhr1). The service domain vecta-consultancy-production.up.railway.app serves 200 from the same edge PoP, so the deployment is healthy.
Already tried: reissuing the cert, deleting+recreating the domain (via API and via the dashboard), and redeploying (fresh SUCCESS deployment). The edge still won't route the custom domain. Please force-sync/clear the stuck edge route for this hostname. Note: RAILWAY_PRIVATE_DOMAIN is aieli-consultancy.railway.internal (service was renamed) — flagging in case a stale mapping is involved.
Pinned Solution
a month ago
You need to add a TXT record for _railway-verify.www.vectaconsultancy.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
You need to add a TXT record for _railway-verify.www.vectaconsultancy.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
darseen
You need to add a TXT record for `_railway-verify.www.vectaconsultancy.com`. If you are using the API to add your custom domain, you can find it in `verificationToken` under `status`.
a month ago
All is working now thank you
Status changed to Solved 0x5b62656e5d • 28 days ago