The certificate has CN=*.nuget.org but is missing a SAN for the root (nuget.org) which is leading to certificiate validation issues.
(net::ERR_CERT_COMMON_NAME_INVALID in Chrome.)
Possibly related to #3490
@j3parker, thanks for the report. We have reverted the certificate change. Could you try accessing https://nuget.org/ again?
The certificate is now valid (CN = nuget.org with a Subject Alternative Name including *.nuget.org) but nuget.org is doing a very slow 301 to www.nuget.org, oddly.
EDIT: so things should work, although the slowness is probably an issue.
Slowness is likely related to app warm-up time. Please let us know if the slowness persists.
Thanks!
Most helpful comment
Slowness is likely related to app warm-up time. Please let us know if the slowness persists.