Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Untrusted site, no option to click I understand the risks

  • 9 replies
  • 59 have this problem
  • 19 views
  • Last reply by WmHayashi

more options

So someone screwed something up on the proxy servers here at work (at least that's all we can figure out). When I try to go to Google.com, I get one of those Untrusted Sites warning messages that it is trying to connect to accounts.google.com and can't verify that it's secure.

Problem is, I don't have the option to click I understand the Risks and tell it to just go through anyway. I only get the option to Leave or view the details.

Is there any way to add accounts.google.com to an exception list or anything like that so I can just force it to work? Or is there any way to force the Understand Risks area to show up so I can do the Add Exception thing?

Thanks.

So someone screwed something up on the proxy servers here at work (at least that's all we can figure out). When I try to go to Google.com, I get one of those Untrusted Sites warning messages that it is trying to connect to accounts.google.com and can't verify that it's secure. Problem is, I don't have the option to click I understand the Risks and tell it to just go through anyway. I only get the option to Leave or view the details. Is there any way to add accounts.google.com to an exception list or anything like that so I can just force it to work? Or is there any way to force the Understand Risks area to show up so I can do the Add Exception thing? Thanks.

All Replies (9)

more options

Check the pref browser.xul.error_pages.enabled on the about:config page and make sure that the value is set to true (default).

Check and tell if its working.

Modified by Hasan

more options

That setting was set to True but the one underneath it was set to False. I set that one to True and then I did get the Add Exception box. However, when I click it to add the exception, it didn't do anything.

more options

You can check who issued that certificate.

You can retrieve the certificate to check who issued the certificate. You should always do that to see if that helps to identify the problem (missing intermediate certificate or something else).

-> click the link at the bottom of the error page: "I Understand the Risks"

-> Let Firefox retrieve the certificate: "Add Exception" -> "Get Certificate".

  • click the "View..." button to inspect the certificate and check who is the issuer.

-> Only leave the checkmark in the box at the bottom to "Permanently store this exception" if you trust that certificate.

  • click "Confirm Security Exception" to enter the site if you still want to go to that website.

-> Secure connection failed and Firefox did not connect

Check and tell if its working.

Modified by Hasan

more options

Issues to: Google. Issued By: Our internal proxy server

I checked the box and clicked Confirm but it still goes right back to the Untrusted page. It's just not taking.

more options
more options

Tried all that. Didn't help.

more options

From the image it looks like SSL proxying is not working, so you may be able to entirely disable SSL for the browsing session in Tools (Alt + T) > Options > Advanced > Network > Settings or at least exempt .google .com

more options

You write: Issued By: Our internal proxy server

You seem to be using a proxy server that makes its own secure connection to the server and that send a certificate to to Firefox.
Such a setup will only work properly if you can install a root certificate from that proxy server.
If you do not need to use that proxy server then choose a direct connection.

more options

Okay, I tried all the suggestions already mentioned above and they didn't work. The system I'm using is a Ubuntu 11.10 with Firefox 11.0. Here's the way I worked around the problem:

1. Started Firefox and went to the "offending site." 2. Opened a new tab and entered "about:certerror" and got the add exception panel (finally). 3. Copied the URL of the offending site from the first tab and pasted it into the URL field of the exception panel. 4. Followed the directions to make the exception permanent.

What a pain in the butt to get there {grin}!

Happy computing...

WmH