2 months ago
Title: Custom domain has VALID cert but edge returns 404 "Application not found" (x-railway-fallback)
ai-usage.acumon-intelligence.com will not route despite a valid cert and correct DNS.
- Project: AI-Dashboard — c609547f-d0a2-4091-950b-a3bd84a37bd1
- Environment: production — 605e26b5-cb5b-41fb-ab3d-a7fe63c4171e
- Service: web-v2 — 465b926e-3a2e-4b3c-910d-397aac72eb67
- Custom domain: ai-usage.acumon-intelligence.com (DNS-only CNAME -> u148v1w2.up.railway.app, propagated)
Symptom: HTTPS completes the TLS handshake with the correct VALID cert, but every
request returns HTTP 404 with header x-railway-fallback: true and body
{"status":"error","code":404,"message":"Application not found"}. The service's own
domain web-v2-production-1921.up.railway.app serves 200 at the same time — so the
edge has the domain + cert but no host->service route.
Tried (no change): removed & re-added the custom domain; customDomainIssueCertificate
(-> VALID); targetPort 3000 and auto; multiple redeploys + a restart; and a full
service recreate (web-v2 is brand new). The fallback 404 persists throughout.
Request: please reconcile/repair the edge routing for this custom domain.
1 Replies
2 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 2 months ago
2 months ago
Your TXT record is malformed. Make sure you're copying the exact string Railway provided when adding your domain. You can access the content for the record from the verificationToken property under status.