Forum Discussion
ERR_CERT_COMMON_NAME_INVALID
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.
Eric_Lawrence Thank you! I'm not a web developer, but is there anything I can do to report this?
- RobertoSAGMar 10, 2020Copper Contributor
Eric_Lawrence Yeah, I'm in Brazil, and that makes sense. Thank you for the assistance!
- Eric_LawrenceMar 10, 2020
Microsoft
The Twitter team reports that they're working on it; see the "reached out to" link above. (I'm presuming that you're located somewhere near Brazil; if not, it might be helpful for you to share a bit more info so I can make sure that they fix this everywhere that is impacted).