a month ago
I added 11 wildcard custom domains (*.buildr.beer, *.buildr.lol, *.buildr.surf, … 11 different TLDs) to one service. All 11 verified ownership
successfully (verified=true) and moved to certificateStatus=ISSUING, certificateStatusDetailed=POLLING_AUTHORIZATIONS — and have been stuck there 30+ minutes.
I've verified the DNS is fully correct:
- _railway-verify. TXT present → ownership verified=true
- _acme-challenge. CNAME → .authorize.railwaydns.net, and the ACME validation TXT resolves identically from Cloudflare/Google/Quad9/OpenDNS
- No CAA records blocking on the domains or their TLDs
- certificateErrorType=None, certificateRetryable=None — no errors reported
Looks like the Let's Encrypt orders are stuck. Can you manually retry/kick the cert issuance for these wildcard domains? Happy to provide the domain IDs.
Pinned Solution
a month ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
4 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
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
a month ago
Yea I came back and it said "contact support" idk why railway still has the worst support in existence.
a month ago
mfs are so lazy they can't even do support themselves just rely on other people is crazy
a month ago
obv if it was something that can be supported be mods I'd make it a mod request railway. god I hate this company sm
Status changed to Solved 0x5b62656e5d • 16 days ago