3 months ago
My CNAME is verified via nslookup but the dashboard is stuck on "Waiting for DNS update". So when i try to load my www site, i get "net::ERR_CERT_COMMON_NAME_INVALID"
I don't have any conflicting DNS records and no CAA restrictions.
Can Railway just kick the process?
Pinned Solution
2 months ago
You have not set the TXT record.
3 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
Your DNS for www.caddiecard.com looks correct - the CNAME points to Railway and resolves to our IP range. Since the DNS is properly configured, try removing the custom domain from your service settings and re-adding it to trigger a fresh certificate issuance. Only do this once, as Let's Encrypt enforces rate limits (5 duplicate certificates per domain per week). Certificate issuance typically completes within an hour after re-adding.
Status changed to Awaiting User Response Railway • 2 months ago
sam-a
Your DNS for www.caddiecard.com looks correct - the CNAME points to Railway and resolves to our IP range. Since the DNS is properly configured, try removing the custom domain from your service settings and re-adding it to trigger a fresh certificate issuance. Only do this once, as Let's Encrypt enforces rate limits (5 duplicate certificates per domain per week). Certificate issuance typically completes within an hour after re-adding.
2 months ago
Thanks for the response. I just tried this and still see the same "Waiting for DNS" (see screenshot)
Attachments
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved brody • 2 months ago