Explore tweets tagged as #ERR_CERT_COMMON_NAME_INVALID
@barrelltech Hey Benjamin, I was just checking your app Phrasing (excellent design, btw) from the HN thread (the playground link returns a 404) and trying to access the blog returns an SSL Cert error (net::ERR_CERT_COMMON_NAME_INVALID).
1
0
1
一部の環境でTweetDeck を開こうとすると、証明書エラー(NET::ERR_CERT_COMMON_NAME_INVALID)が原因で接続できない問題、Twitterさんにまともに取り合ってもらえる窓口が見つからなかったので ダメ元でイーロン・マスクさんに直訴しておいた…
@elonmusk Hello. Many Japanese users cannot access because they receive a message stating "Your connection is not private". It appears that some of the servers hosting TweetDeck may have incorrect TLS certificates installed. I
1
2
4
Hi @rustdesk, I just noticed that runs on the CN certificate (without a subdomain) which results in `NET::ERR_CERT_COMMON_NAME_INVALID`. I know it's beta, but still would appreciate fixing it (;
1
0
0
@moranbar @KarlikLimor Your connection is not private.Attackers might be trying to steal your information from (for example, passwords, messages or credit cards). Learn more.net::ERR_CERT_COMMON_NAME_INVALID.
1
0
2
@usslibertyvets "Your connection is not private.Attackers might be trying to steal your information from (for example, passwords, messages, or credit cards). Learn more about this warning.net::ERR_CERT_COMMON_NAME_INVALID".
0
0
0
How-To Fix Your PC: How to Fix a NET::ERR_CERT_COMMON_NAME_INVALID Privacy Error via @howtogeek
0
0
0
@u83unlimited なるほど、XのWebViewだと自分も再現しました.NET::ERR_CERT_COMMON_NAME_INVALIDになりますね.ありがとうございます、報告しておきます.
0
0
1