Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

From this morning I get this error whenever I access Google Docs and some websites. My system datetime is correct and I checked "Automatically from the Internet". My BIOS is OK. I cleared everything (cache, cookie, private data) in Chrome and restarted OS but nothing changes. How to fix it? Firefox works but Chrome has that problem.

The site's security certificate is not trusted!

You attempted to reach docs.google.com, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Google Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications.

You cannot proceed because the website operator has requested heightened security for this domain.

enter image description here

share|improve this question
2  
Seems Google don't trust themselves anymore.. –  Herman Torjussen Jul 26 '12 at 10:20
    
Could my company block those sites? I think it could happen... –  Emerald214 Jul 26 '12 at 10:43
    
@Emerald214 - Ask your company. –  Ramhound Jul 26 '12 at 10:51
3  
This can happen if someone is re-routing you through a decrypting proxy. This is done in some corporates and dictatorship countries. –  Robert Jul 26 '12 at 11:15
    
@Emerald214: It's not that they block it, it's that they insist on decrypting and re-encrypting it. Usually the stated reason is so that they can check for malware and the like. However, this requires you to explicitly configure your browser to trust them because, obviously, if a malicious entity did that, it shouldn't work. –  David Schwartz Jan 12 '13 at 15:55
add comment

2 Answers 2

up vote 1 down vote accepted

Please try the following solutions:

  • Check your system datetime again, set to manual to make sure that you have todays date (2012 at least). See: Chrome bug #41886

  • Check if your hosts file is not hacked.

  • Check the Chrome plugins, if you don't see anything weird.

  • Check different browsers if it works.

  • And at last, run your Chrome browser from Terminal, it'll give you more details about the error.

share|improve this answer
add comment

Create a new profile in Chrome

share|improve this answer
    
Can you please explain why you believe that would help? –  Scott Jun 10 '13 at 18:45
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.