ArchTech Posted May 23, 2017 Posted May 23, 2017 (edited) Dear All One of the Mac's in the room have an issue where it cannot connect to any HTTPS website via Chrome. It said: Your connection is not private Attackers might be trying to steal your information. Adavanced NET::ERR_Cert_Invalid I think this is due the certificates expiring. If you have any information or know anything please let us know. Thank you Regards Archtech Edited May 23, 2017 by ArchTech
twelvetree Posted May 23, 2017 Posted May 23, 2017 These sort of issues are often as a result of Proxy. We have a Protex filtering system and we had to download a certificate from them to access Google (and obviously Chrome). This is their link page: Installing ProtexRootCA certificates It explains what the problem is. Maybe your filtering system has a similar set up?
aarongulley Posted May 24, 2017 Posted May 24, 2017 What is the name of your filtering system? They inspect SSL certificates... Generally you'll get given a certificate which acts like a certificate for Google Thanks Aaron.
ArchTech Posted May 24, 2017 Author Posted May 24, 2017 Dear All All the other Mac's in the room work fine so it cant be the proxy. It only seems to be affecting this one Mac. Is there not a way we can force the Mac to accept the certificate in any way? Thank you for replying everyone. Regards ArchTech
aarongulley Posted May 24, 2017 Posted May 24, 2017 Yes, open Keychain Access and find the certificate and double click it on and where it says "When using this certificate:" change it to "Always trust" and it will prompt you for login password enter that and it will be all okay. Thanks Aaron.
twelvetree Posted May 24, 2017 Posted May 24, 2017 Also if there are different users make sure the certificate is in system in the keychain access so it is valid for all users. 1
aarongulley Posted May 24, 2017 Posted May 24, 2017 Also if there are different users make sure the certificate is in system in the keychain access so it is valid for all users. Yes remember to drag it to System
ArchTech Posted May 26, 2017 Author Posted May 26, 2017 Dear aarongulley We have done the trust certificate way and for some reason keychain does not hold the setting for some reason, we have done this as local admin and root user. Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now