Domain Validation Stuck on "Validating Domain Ownership"
kumar3p02
HOBBYOP

2 months ago

Domain validation for api.khiru.in is stuck on "Validating domain ownership" for 12+ hours and won't complete.

Solved

3 Replies

Railway
BOT

2 months ago

Your DNS records for api.khiru.in are correctly configured and propagated, verification has passed, and your service is deployed, but the certificate is stuck in the "validating ownership" state. Per our SSL troubleshooting docs, you can try removing the custom domain and re-adding it once to restart certificate issuance, but do not repeat this more than once as Let's Encrypt enforces a rate limit of 5 duplicate certificates per domain per week.


Status changed to Awaiting User Response Railway about 2 months ago


Railway

Your DNS records for `api.khiru.in` are correctly configured and propagated, verification has passed, and your service is deployed, but the certificate is stuck in the "validating ownership" state. Per our [SSL troubleshooting docs](https://docs.railway.com/networking/troubleshooting/ssl), you can try removing the custom domain and re-adding it once to restart certificate issuance, but do not repeat this more than once as Let's Encrypt enforces a rate limit of 5 duplicate certificates per domain per week.

kumar3p02
HOBBYOP

2 months ago

I already removed and re-added and it's been hours but still certificate not issued


Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

Hey,

Sorry about that. We have rolled out a fix for this. Your domains should automatically get issued a certificate. If they don't, please remove and re-add the domain.


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

2 months 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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...