20 days ago
Two custom domains are stuck on _railway-verify TXT verification and have not been issued certificates after 48+ hours. DNS is correct and confirmed resolving worldwide.
Both TXT tokens match what the dashboard requests. CNAMEs are green.
Only the TXT verification is stuck, which is blocking certificate issuance.
Ruled out on my side: TXT resolves correctly on both public resolvers, no CAA records (so Let's Encrypt is allowed), DNSSEC not enabled (no DS record), no stale _acme-challenge records, and the GoDaddy host entries are zone-relative and correct.
Already tried: waited 48+ hours and confirmed DNS on Google and Cloudflare.
Request: this looks like backend verification stuck despite correct DNS. Please force verification and certificate re-issuance for both custom domains.
The form only allows one service selection. The other service in this same project has the identical issue and needs the same fix.
1 Replies
Status changed to Awaiting Railway Response Railway • 20 days ago
19 days ago
We confirmed that the CNAME and TXT verification records for both custom domains on that project are propagated and match the expected values. We have initiated a certificate re-issuance for both, which may take a few minutes.
Status changed to Awaiting User Response brody • 19 days ago
Status changed to Solved hexman-12 • 19 days ago