a month ago
Hello Railway team,
My custom domain achagov.com.br has been stuck on “Waiting for DNS update” for more than 6 hours.
Project: achagov-v0
Environment: production
Service: achagov-web
Custom domain ID: ee0b23cd-9d66-4471-b3aa-2540700d9827
The authoritative nameservers are already active:
elliott.ns.cloudflare.com
mia.ns.cloudflare.com
Both required DNS records are correctly configured in Cloudflare with proxy disabled (DNS only):
CNAME @ -> 8bcbzud1.up.railway.app
TXT _railway-verify ->
railway-verify=36aaa7ab6d3e7bf7395f7e2e216debe22c21479a96a290f7c65fa6f006ea8e93
The TXT record resolves publicly and exactly through 1.1.1.1.
The Railway CLI reports:
Sync status: ACTIVE
Verified: no
Certificate status: CERTIFICATE_STATUS_TYPE_ISSUING
Running:
railway domain certificate retry achagov.com.br
returns:
Certificate retry is only available after certificate issuance fails.
Current status: CERTIFICATE_STATUS_TYPE_ISSUING.
The browser currently receives Railway’s default certificate and reports:
NET::ERR_CERT_COMMON_NAME_INVALID
Could you please force domain re-verification and restart/reissue the certificate for this domain?
Please do not delete or recreate the custom domain because the current DNS records and verification token are already propagated.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
Your DNS records are correctly configured and the verification TXT matches, but the certificate workflow stalled before it could pick up the completed verification. We've started a certificate re-issuance, which should complete within a few minutes.
Status changed to Awaiting User Response ray-chen • 28 days ago
21 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 21 days ago