a month ago
Custom domains http://www.smsworkboat.co.uk and demo.smsworkboat.co.uk (Hobby plan) are stuck on "validating challenges" — the CNAMEs verify
▎ (green tick) but the TLS certificate hasn't issued in 8+ hours; both still serve the default *.up.railway.app cert. I've worked through
▎ your entire cert-troubleshooting guide: DNS is propagated and correct (CNAME → the Railway-provided target; TXT railway-verify=9d3c2c45…
▎ live at @, confirmed via public DNS and dnschecker), no CAA records, no DNSSEC (no DS/DNSKEY), not using Cloudflare, no conflicting A/CNAME
▎ on the same host, and the target services return HTTP 200. I've also removed/re-added the domain and isolated the TXT — no change. Please
▎ force certificate issuance or investigate why the Let's Encrypt challenge isn't completing on your edge.
Pinned Solution
a month ago
You need to add a TXT record to _railway-verify.www.smsworkboat.co.uk and _railway-verify.demo.smsworkboat.co.uk. If you’re using the API, you can find the content for the record from the verificationToken property 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 • 29 days ago
a month ago
You need to add a TXT record to _railway-verify.www.smsworkboat.co.uk and _railway-verify.demo.smsworkboat.co.uk. If you’re using the API, you can find the content for the record from the verificationToken property under status.
a month ago
Nailed it! Thank you
Status changed to Solved 0x5b62656e5d • 29 days ago