a month ago
Hey team,
Hoping you can help unstick a custom domain that seems to be stuck on your end rather than ours.
Domain: demo.triptease.com
Custom domain id: 25921a8b-16c9-415e-9e95-00ca385a0789
Project: Messages Demo
Service: code-messages-demo
DNS is fully correct and propagated, CNAME demo.triptease.com -> 2m7kbrzy.up.railway.app, and the TXT record at _railway-verify.demo matches your expected verification token exactly (confirmed via dig and host from our side).
certificateStatus is showing as VALID/COMPLETE too, and I can see via direct TLS inspection that a cert has actually been issued for demo.triptease.com specifically.
But the domain's verified field is still stuck on false, and hitting https://demo.triptease.com/ still gets a 404 from your edge (railway-hikari) with "Application not found". I manually triggered customDomainIssueCertificate a while back which is presumably what got the cert issued, but it's been well over 30 minutes since and verified/routing hasn't budged, so it doesn't seem to be a propagation timing thing anymore, more like it's just stuck. I also double checked the TXT record across Google, Cloudflare and Quad9 resolvers and it's consistent everywhere, so I don't think this is a DNS propagation issue on our side at all.
I did come across a community post with what sounds like the exact same symptom (cert VALID, DNS propagated, edge still 404 "Application not found"), where it turned out the edge upstream mapping for the hostname just never synced, and needed someone on your side to manually rebuild the routing. Wondering if we're hitting the same thing here.
One extra thing that might be relevant, we think there may be a second Railway account or workspace with something set up under the same root domain (reports.triptease.com -> i9sezk6r.up.railway.app, a different CNAME target to ours). We're not 100% sure if that's the same Triptease account or a separate one, but flagging it in case it's causing some kind of cross-account contention on the root domain verification.
Could someone take a look and manually push this through?
Thanks,
Niko
1 Replies
a month 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 1 month ago
a month ago
If you haven't tried it already, remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again. This usually fixes the stuck state.