a month ago
My custom domain validation is stuck in the “Validating” status. I have already added the required details to my domain service provider, but it is still pending validation.
7 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your DNS records are correctly configured and domain ownership is verified, but the certificate issuance pipeline stalled before completing. We've started a certificate re-issue for your domain, which should complete within a few minutes.
Status changed to Awaiting User Response brody • about 1 month ago
brody
Your DNS records are correctly configured and domain ownership is verified, but the certificate issuance pipeline stalled before completing. We've started a certificate re-issue for your domain, which should complete within a few minutes.
a month ago
I still have the same issue.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your DNS records and domain verification are still correct, but the certificate remains stuck in the validation step despite the earlier re-issue. We've started another certificate re-issue for your domain, which should complete within a few minutes.
Status changed to Awaiting User Response brody • about 1 month ago
brody
Your DNS records and domain verification are still correct, but the certificate remains stuck in the validation step despite the earlier re-issue. We've started another certificate re-issue for your domain, which should complete within a few minutes.
a month ago
Do I need to wait more days? It has still been validating for 4 days now.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
No, you should not need to wait days. We found an A record pointing to a non-Railway IP address on your root domain alongside the CNAME. Railway does not support A records for custom domains, and this is likely preventing the certificate from completing validation. Please remove the A record for your root domain in Namecheap so that only the CNAME pointing to Railway remains. We've triggered another certificate re-issue, which should complete once the A record is removed.
Status changed to Awaiting User Response Railway • about 1 month ago
brody
No, you should not need to wait days. We found an A record pointing to a non-Railway IP address on your root domain alongside the CNAME. Railway does not support A records for custom domains, and this is likely preventing the certificate from completing validation. Please remove the A record for your root domain in Namecheap so that only the CNAME pointing to Railway remains. We've triggered another certificate re-issue, which should complete once the A record is removed.
a month ago
only these records are available in Namecheap side
Attachments
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We can still see an A record resolving for your root domain alongside the CNAME. Looking at your screenshot, the "URL Redirect Record" at @ is the only record that could be producing it. Please remove that URL Redirect Record in Namecheap, then verify the A record is gone (you can check at a site like dnschecker.org). Once only the CNAME remains, the certificate validation should complete.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago
