2 hours ago
Hi — my custom domains have been stuck for over 12 hours despite everything showing green in the API/dashboard.
Project: d1cb9f16-0843-40c1-b99b-85e9fd6a54d9 — service site (5e167644-2754-4c48-bf9f-901fe9b06f98), environment production
Domains: virginiafrance.com → CNAME (Cloudflare flattening, DNS-only) → 5k7z75ua.up.railway.app ; www.virginiafrance.com → CNAME (DNS-only) → 3vh2z04d.up.railway.app
Current state (verified via GraphQL API): dnsRecords = PROPAGATED for both, certificateStatus = VALID for both.
But the edge doesn't serve the certificates: openssl s_client -servername virginiafrance.com → tlsv1 alert internal error, no certificate served. The SAME edge IP works fine for Railway SNIs (serves CN=*.up.railway.app), and https://site-production-959e.up.railway.app returns 200. Public DNS is correct everywhere (flattened apex A == target A 69.46.46.85). Behavior has been flapping: for a while the edge DID serve CN=virginiafrance.com (with the 404 "train has not arrived" page, request ID lQZU9smSR1CVcYtlrJsmnA), then regressed to TLS failure.
Already tried: domain delete → 20 min wait → re-add (twice), customDomainIssueCertificate mutation (returned true), multiple redeploys (latest SUCCESS at 15:12 UTC today).
Could you rebind the custom-domain routing/certificate configuration on the edge for this service? Everything user-side checks out. Thanks!
2 Replies
an hour 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 • about 2 hours ago
an hour ago
Your website is working as expected on my end.
Valid certificate and I see all records on a nslookup.
an hour ago
Your domain is working just fine. It might be a caching issue, try to access it from an incognito tab, or use a different network.
Attachments