"Your connection is not private"

I keep getting this error with almost every website I go to, Google, Reddit, Facebook, etc.

"Your connection is not private
Attackers might be trying to steal your information from Google (for example, passwords, messages, or credit cards).
NET::ERR_CERT_COMMON_NAME_INVALID"



I get a similar error with Firefox, Internet Exploder, and Edge. This has been going on ever since the other night when my roommate decided there was something wrong with the internet (was working fine for everyone else) and did something to it in an attempt to "fix it." She's not home right now, and the person who has the internet in their name isn't, either, so I can't contact AT&T to fix it. How can I fix this myself?

Nope. My phone and both my tablets, too.

Bree all OS's are doing that now when it comes to WEP or no security. I have seen it on WPA/WPA2 Mixed for the service that Holiday Inn Suites use.

Wullail said:

Yeah , sounds like the routers encryption has been turned off , check the properties of the wifi connection and see what it says.

Sometimes it is actually the device that is the culprit. With the changes to iOS 10, you get a whole new type of message when you are on a unsecured network, even if it is using WPA/WPA2.

Mystere said:

Sounds like they did something on the router that is filtering secure traffic, which typically involves installing a self-signed certificate to decode the traffic, analyze it, then re-encode it.

Regardless, unless you have access to the router password, probably nothing you can do.

^ This.

Your connection is being Man-In-The-Middled by something. Therefore your browsers are warning you that the Common Name on the TLS certificates are different to the URL's displayed in the address bar of your browser. I.E. The Common Name on the TLS Certificate for www[.]google.com isn't actually showing www[.]google.com as it should be.

You need to speak to the person who owns the router/internet connection (the bill payer) as you're roommate shouldn't be screwing with the router in this way. Assume everything you've done during the time when you've been receiving the warnings has been read by someone else in plain text, including all usernames and passwords. Therefore if you were able to bypass the browser warnings, once the problem has been rectified and you're no longer receiving the warnings, you're going to need to change all passwords that have been used during that time.

If you go to www[.]google.com in Internet Explorer, then click on the padlock in the address bar > View Certificates (you can't do this in Edge), the below pic is what the Google TLS Certificate should look like. You'll probably find something else showing instead of www[.]google.com, hence the warnings. But that's of course if the browser will even let you, because poor browser design quite often means it's not possible to see the certificate that's causing the errors. I very much doubt there will be an actual padlock on your computer due the cert error, but it may or may not give you the possibility to still view the certificate causing the error.