Forum Discussion
ERR_CERT_COMMON_NAME_INVALID
Eric_Lawrence I'm actually at home accessing the Internet via a Century Link C2100Z appliance. While Century Link may have a ZScaler somewhere up the line, I won't have any access to it.
That said, if I switch to my other laptop (which is still using the native Windows 10 Edge browser) and browse these sites from the same network, I have no issues. So again, it seems that something is fishy with the browser (or at least the Windows 10 laptop that the Edge Dev browser is running on).
<Todd />
msedge.exe --disable-features=PostQuantumCECPQ2
<Todd />
- Eric_Lawrence
Microsoft
Hi, Todd-- The other explanation is that you're behind some sort of misconfigured device or there's malware causing the issue.
Sharing the full certificate info of an incorrect certificate (see https://textslashplain.com/2017/03/30/get-help-with-https-problems/ ) or a Network Log (https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/) would allow me to tell you what specifically is happening.Eric_Lawrence Hi! The same problem is happening to me, and only in a specific situation: when accessing Twitter from an email I got on my Gmail saying I have a new Direct Message. If I click on the link from there, this happens. If I access Twitter from any other means, it works fine.
The certificate information and the network log are in attachment, in the same ZIP file.
- Eric_Lawrence
RobertoSAG The immediate problem is that the certificate (thumbprint d4b95942dea3f885dc782634cbcc0c8cabe82b4c) being presented for "www.twitter.com" does not contain "www.twitter.com", only "twitter.com". The live certificate I see for Twitter when navigating to it from Texas, USA includes both. When navigating to Twitter from Brazil, I get the certificate lacking the "www." I reached out to Twitter Engineering.
It appears that either Twitter mis-issued this certificate (it should have included the "www." prefix), or misconfigured their servers such that a server which was supposed to use a "www." certificate instead chose the certificate that omitted the "www." entry.
