Custom Domain pending verification

Hello,
I’m having trouble with my custom domain being stuck in “Pending Verification” for almost 24 hours now. I’ve never had this problem in the past, it usually verifies within a few minutes. I’m not sure what / if I am doing anything wrong, but based on dig it appears I have set up the CNAME correctly.

dig login.dionny.dev

;; QUESTION SECTION:
;login.dionny.dev.		IN	CNAME

;; ANSWER SECTION:
login.dionny.dev.	300	IN	CNAME	dionny-dev-subscription-finder-cd-2g0pnftphdya8ezv.edge.tenants.us.auth0.com.

Please advise and thank you in advance!

Hi @dionny,

Welcome to the Auth0 Community!
It is not uncommon for the verification process to take up to 48 hours, even though we regularly see this get completed sooner, as you mentioned.
I would advice to allow it some more time before attempting any troubleshooting, but if this persists, please check our documentation on this.

Have a great one!
Gerald

Thanks for your response!

It has now been over 48 hours and the custom domain is still pending verification. I’ve tried clicking the Verify button after waiting 4 hours several times and no luck.

I’ve gone through all of the troubleshooting steps you’ve linked to no avail. Everything appears to be set up properly on my end.

I suspect there is an issue with the SSL certificate on your end, as when I visit login.dionny.dev I get an invalid SSL certificate error.

Please help as I am currently blocked by this problem. Thanks very much!

In case someone else runs into this problem, here’s how I resolved the issue:

  1. Deleted the custom domain config in Auth0 for the ‘stuck’ domain
  2. Created a new CNAME DNS entry foo.dionny.dev (throwaway) and configured Auth0 with this domain. This verified successfully after about 3 minutes.
  3. Deleted the throwaway custom domain config in Auth0
  4. Deleted the CNAME DNS entry for login.dionny.dev, re-created the custom domain config in Auth0 for login.dionny.dev
  5. Finally, re-created the CNAME DNS entry for login.dionny.dev. This verified successfully after about 3 minutes.

Much better than waiting 48 hours :slight_smile:

1 Like

Hi @dionny
Thank you for sharing this with the Community!

1 Like