Today, when trying to login using the Lock widget the attempt is blocked by both Chrome and Safari (Chrome: “Your connection is not private”). This has been working for many months. The reason for the error is that the wrong certificate is presented from my-app-name.eu.auth0.com. Here are the certificate details: ![alt text]
It seems like something has gone wrong at Auth0 or GoDaddy, perhaps when rotating certificates. Any ideas about how to resolve this?
curl -iv https://[my-account].eu.auth0.com/test:
* Rebuilt URL to: https://[my-account].eu.auth0.com/ * Trying 184.108.40.206... * TCP_NODELAY set * Connected to [my-account].eu.auth0.com (220.127.116.11) port 443 (#0) * SSL certificate problem: Invalid certificate chain * Curl_http_done: called premature == 1 * Closing connection 0 curl: (60) SSL certificate problem: Invalid certificate chain More details here: https://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.