The certificate is valid, unexpired, and CA-signed — and the browser still refuses it with NET::ERR_CERT_COMMON_NAME_INVALID, because it was issued for a different hostname than the one you typed. Why the Common Name no longer counts, the causes in the order they bite, and how to read the SAN list your server actually presents.
The certificate is real. It's signed by a genuine CA, it's nowhere near expiry, and the chain is complete. And the browser still slams the door:
Your connection is not private
NET::ERR_CERT_COMMON_NAME_INVALID
Enter fullscreen mode
Exit fullscreen mode
The chain is complete and the hostname matches — and the browser still refuses it with NET::ERR_CERT_AUTHORITY_INVALID, because…
It works in your browser and fails in curl, Node, or Python with "unable to get local issuer certificate." That almost always…
You finally did it. You installed Burp Suite. Configured the proxy. Opened your browser. Visited...
Your site was fine yesterday. This morning every browser is throwing a full-page security warning,...
Chunghwa Telecom and Netlock customers must look elsewhere for new certificates.
An unauthorized certificate for your domain never touches your server, so your monitoring never sees it — but it is public in the…
