readthedocs.org: SSL_ERROR_BAD_CERT_DOMAIN for assets.readthedocs.org

Looks fixed here, thank you.

We got confirmation that the Azure team has repaired the CDN SSL termination. Can anyone still reproduce this issue or confirm the fix has worked? I wasn’t able to reproduce this yesterday either, but that was locally here in the west US.

Same problem, same CN, same IP 13.107.246.10 at the end of CNAME resolve like in two comments above. Slovakia.

In case anybody runs across this, we are still seeing this very intermittently. If you have any details on your setup (browser, country/region, OS) that would be helpful.

The command to test this in OpenSSL is:

openssl s_client -connect assets.readthedocs.org:443 -showcerts -servername assets.readthedocs.org | grep CN=

If you see CN=assets.readthedocs.org in the response, it’s good. If instead you see *.azureedge.net then it is not correct.

Ok, I sshed into a bunch of different servers and found one (US East) that exhibits the issue. I don’t think there’s much I personally can do here so I’m going to try to escalate this to Microsoft.

That looks like Firefox on Windows. Is that correct? If you wouldn’t mind could I get the exact version number and at least the major OS version? You aren’t by chance running a nightly or anything, right? Are you seeing this exclusively on Firefox? Not other browsers?

There’s nothing on Azure’s status page although I don’t fully trust status pages. It also says the “certificate successfully deployed” in our Azure dashboard. Nothing relevant on Twitter. It’s still a bit of a mystery to me…

Interestingly, I tried through curl and I got an error on the very first try. Every retry since then has succeeded.

$ curl -IL https://assets.readthedocs.org/static/images/body-bg.944990822890.svg
curl: (51) SSL: no alternative certificate subject name matches target host name 'assets.readthedocs.org'