Søg i 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

How to I stop FF from loading every website using HTTPS

  • 2 svar
  • 2 har dette problem
  • 2 visninger
  • Seneste svar af xladlk

more options

FF is trying to initially load every website using HTTPS including mozilla.org. Then I get the Connection Untrusted error of course. The one for Mozilla .org is "invalid security certificate" and "issuer of certificate is unknown". I tried deleting the cert8.db file as suggested other places but that didn't help. If there is a option for this somewhere, I can't find it. I have the latest version of FF and running Win7. Thanks for the help.

FF is trying to initially load every website using HTTPS including mozilla.org. Then I get the Connection Untrusted error of course. The one for Mozilla .org is "invalid security certificate" and "issuer of certificate is unknown". I tried deleting the cert8.db file as suggested other places but that didn't help. If there is a option for this somewhere, I can't find it. I have the latest version of FF and running Win7. Thanks for the help.

Valgt løsning

There must be some sites that don't yet use a secure connection, such as http://www.amazon.com/. If even a link to Amazon gets redirected, you might check whether you have an extension like HTTPS Everywhere.

For Mozilla sites, yes, you need to make a secure connection.

But you shouldn't get certificate errors! When you get this for pretty much all secure sites, the problem usually is one of the following:

(1) Error in your system's date, time, or time zone, which throws off certificate validity checks. Sometimes allowing computers to use an internet-based time source can introduce this problem.

(2) Firefox not being set up to work with your security software that intercepts and filters secure connections. Products with this feature include Avast, BitDefender, ESET, Kaspersky; AVG has a Search Shield feature which can cause this error on search sites.

(3) Malware on your system intercepting secure connections.

So... which is it?

If you have any of those specific security products, that would be the first thing to check. We might be able to assist with specific next steps based on what you have if you tell us.

Alternately, you can examine the certificate to which Firefox is objecting to see whether the issuer information points to the culprit. Take my test page for example:

https://jeffersonscher.com/res/jstest.php

You should see an "I understand the risk" heading in the page. If you expand that section, you should find an Add Exception button. You don't need to complete the process of adding an exception (I suggest not adding one until we know this isn't a malware issue) but you can use the dialog to view the information that makes Firefox suspicious.

Click Add Exception, then View. If View is not enabled, try the Get Certificate button first. Then in the Certificate Viewer, look at the "Issued by" section. What do you find there, and/or under Certificate Hierarchy? I have attached a screen shot for comparison.

Læs dette svar i sammenhæng 👍 1

Alle svar (2)

more options

Valgt løsning

There must be some sites that don't yet use a secure connection, such as http://www.amazon.com/. If even a link to Amazon gets redirected, you might check whether you have an extension like HTTPS Everywhere.

For Mozilla sites, yes, you need to make a secure connection.

But you shouldn't get certificate errors! When you get this for pretty much all secure sites, the problem usually is one of the following:

(1) Error in your system's date, time, or time zone, which throws off certificate validity checks. Sometimes allowing computers to use an internet-based time source can introduce this problem.

(2) Firefox not being set up to work with your security software that intercepts and filters secure connections. Products with this feature include Avast, BitDefender, ESET, Kaspersky; AVG has a Search Shield feature which can cause this error on search sites.

(3) Malware on your system intercepting secure connections.

So... which is it?

If you have any of those specific security products, that would be the first thing to check. We might be able to assist with specific next steps based on what you have if you tell us.

Alternately, you can examine the certificate to which Firefox is objecting to see whether the issuer information points to the culprit. Take my test page for example:

https://jeffersonscher.com/res/jstest.php

You should see an "I understand the risk" heading in the page. If you expand that section, you should find an Add Exception button. You don't need to complete the process of adding an exception (I suggest not adding one until we know this isn't a malware issue) but you can use the dialog to view the information that makes Firefox suspicious.

Click Add Exception, then View. If View is not enabled, try the Get Certificate button first. Then in the Certificate Viewer, look at the "Issued by" section. What do you find there, and/or under Certificate Hierarchy? I have attached a screen shot for comparison.

more options

You nailed it: BitDefender. Last time I used this machine was weeks ago and being where I was, cranked up the security protocols. I never reset them and also hadn't changed the timezone back to local time.

The fact I can Reply means things are working again. Thanks.