23 days ago
Both custom domains on my "site" service are stuck at "Waiting for DNS update" (API: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP) for days — TLS certs never issue.
Project b123988e-20f5-44b6-8a76-debafe37e572 (DumpsterBot), service "site" (f594329f-e844-4d0e-9e47-be9c68886c04), production environment.
Domains: dumpsterbot.net (id 8f882097-70b5-4d88-beab-c3b2ed728bb8) and www.dumpsterbot.net (id 66529839-103e-48d2-9c2d-7522b06fff68).
Key evidence — everything matches Railway's own source of truth, yet verification never completes. This is NOT a missing-TXT case:
- The customDomain API's status.verificationToken for each domain matches the live public TXT records CHARACTER-FOR-CHARACTER (live for 24+ hours):
- _railway-verify.dumpsterbot.net TXT "railway-verify=6d8a4436b3604f3e11c025a58a0ffbc9ec5858c08f65932dfb892fec10e892ea"
- _railway-verify.www.dumpsterbot.net TXT "railway-verify=5c4c6981159c34f37c3862cce4f2bffacbcc449813bc6c1b714e5bb5b59095ba"
-
Railway's own dnsRecords check reports the CNAMEs PROPAGATED (www currentValue == requiredValue == ib0udahs.up.railway.app; apex ALIAS -> 0ah65k3o.up.railway.app resolves to the Railway edge; http reaches the service and 301s to https).
-
Both authoritative nameservers (dns1/dns2.registrar-servers.com, queried directly) and Google + Cloudflare resolvers all return the TXT records. No CAA on the zone. ACME HTTP path reaches the edge (404, not redirected). Registrar: Namecheap.
Already tried: re-adding the domains (fresh targets each time), redeploying the service, reopening the DNS modal to force re-checks. The in-dashboard Railway Agent concluded this is "a platform-side verification/caching issue that requires Railway's infrastructure team to investigate and force a re-check" and directed me here.
Note: thread custom-domain-stuck-at-certificate-statu-6ed742ad (2 hours ago) shows another user stuck in VALIDATING_OWNERSHIP today — that one was missing its TXT; ours are present and token-matched, so please don't close this with the standard "add the TXT record" reply.
Please force re-verification / cert issuance for both domains — it looks like the verification checker cached NXDOMAIN from before the TXT records were created and never re-checked. Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • 23 days ago
23 days ago
Your DNS is correctly configured for both dumpsterbot.net and www.dumpsterbot.net - the TXT verification records match and CNAMEs are propagated. The verification workflow stalled before your records were in place and never re-ran. We've triggered certificate re-issuance for both domains, which should complete within a few minutes.
Status changed to Awaiting User Response Railway • 23 days ago
Status changed to Solved sam-a • 23 days ago