I recently added and verified a custom domain for my Auth0 account. The app is built on example.sorrek.io and the custom domain is auth.example.sorrek.io for instance. When I load the auth domain used in my account it redirects me to app domain, which is expected behavior. I reconfigured my app to use the new auth domain for user logins/signups, and it loads that page correctly, except for the fact that it loads it without an https certificate. The app specifically uses the https SSL in the request, and in the network tab in the inspect element it’s correctly using https in the request, but it’s loading it as an unsecure site. How do I resolve this?
Hi @sorrek,
Welcome to the Auth0 Community !
The most probable causes for this issue are that the certificate for your domain has expired or there might be some network-related problems blocking the access to the certificate, as described in this Knowledge Article.
Otherwise, Auth0 only supports Let’s Encrypt or Google Trust for custom domains with managed certificates and an Enterprise subscription is needed in order to manage certificates for custom domains . If the application redirects to an http page instead of https then Auth0 might not be able to find the managed certificate within Let’s Encrypt or Google Trust.
Thanks again for reaching for support and if you have additional questions please do not hesitate to reply to this post.
Best regards,
Remus
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.