Subject:** Custom domain stuck — cert VALID + DNS propagated + sync ACTIVE, but edge returns 404 "Application not found
opendesk24
HOBBYOP

19 days ago

Hi Railway team,

A custom domain is fully configured and the TLS certificate is valid, but the edge keeps returning a 404 "Application not found" fallback for it. I'd like you to force an edge re-sync / re-attach for this domain's route.

Details

  • Custom domain: www.oasiperlamare.it
  • Custom domain ID: ecd7c49d-7217-46a1-befe-3cc514801cc8
  • Service: OpenDesk24 (ID 40adec9b-b14e-4f74-a2b1-84253f052d74)
  • Environment: production (ID f8121dec-98db-4ae4-86c7-51de12e5710e)
  • Edge: edge-6705e5cc5ae5e82ae931d2b1f900f08f
  • Required CNAME target: ab466zj9.up.railway.app

Current state (all green on config side)

  • certificateStatus: CERTIFICATE_STATUS_TYPE_VALID
  • syncStatus: ACTIVE
  • DNS record: DNS_RECORD_STATUS_PROPAGATEDcurrentValue == requiredValue == ab466zj9.up.railway.app (verified externally via 8.8.8.8: www.oasiperlamare.it is a single CNAME to ab466zj9.up.railway.app, no other records)

Symptom

  • https://www.oasiperlamare.it/ → TLS handshake succeeds (cert is valid, ssl_verify_result=0), but the response is:
    • HTTP/2 404, header x-railway-fallback: true, server: railway-hikari
    • body: {"status":"error","code":404,"message":"Application not found"}
  • The Railway-provided domain on the same service, opendesk24.up.railway.app, works correctly (returns the app, HTTP 302). So the service itself is healthy and deployed.

What we already tried (no effect on the edge 404)

  1. The domain was originally stuck ~16h in VALIDATING_OWNERSHIP; we deleted and recreated it (which changed the CNAME target to ab466zj9.up.railway.app) and updated DNS at the registrar accordingly — DNS then propagated and matched.
  2. Ran customDomainIssueCertificate → cert moved to VALID.
  3. Removed an unused apex custom domain on the same service.
  4. Redeployed the PROD service (new deployment succeeded, app healthy).

Despite cert VALID, sync ACTIVE, edge assigned, and DNS propagated, the edge still returns the 404 fallback for this host. Could you please force the edge to (re)attach the route for www.oasiperlamare.it on this service? Happy to provide any further IDs/logs.

Thanks!

$10 Bounty

1 Replies

Railway
BOT

19 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 19 days ago


You need to add a TXT record for _railway-verify.www.oasiperlamare.it If you are using the API to add your custom domain, you can find it in verificationToken under status.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...