Well, one of the reasons that this could happen is that your Date and Time setting on your computer is out and you have to correct it. Also please check your CMOS battery in your device be it a Laptop or Desktop computer as that is what keeps the Date and Time settings in your BIOS.

Another issue may be that the Anti-Virus program that you are using is causing the issue. Try "Disabling" or "Suspending" (a lot of anti-virus programs today have that feature) the anti-virus program, load your web-page and see what happens.

If this works then there might be an update to fix the false-flagging of the web-page from the anti-virus developer.

Please let me know if this helps.

See also:

• https://support.mozilla.org/en-US/kb/troubleshoot-SEC_ERROR_UNKNOWN_ISSUER

You can click the "Advanced" button to expand this section and show extra details. You can click the blue error message to expand this section. If the certificate is not trusted (SEC_ERROR_UNKNOWN_ISSUER) then click "Copy text to clipboard" and paste the base64 encoded certificate chain text in a reply. That will allow us to check details like the issuer of the certificate.

I found a "solution" somewhere else that said to reset (turn off then back on) "Enable application protocol filtering" in my eset NOD32 antivirus program. Since I did that, I've not received the error message. So I went ahead and changed my website to https.

mwrr said

I found a "solution" somewhere else that said to reset (turn off then back on) "Enable application protocol filtering" in my eset NOD32 antivirus program. Since I did that, I've not received the error message.

That's an interesting tip! I started a discussion on the related help article: Secure connection failed and Firefox did not connect. If you would like to participate in the discussion -- since you have direct experience -- here's a link: https://support.mozilla.org/kb/secure.../7169.)

jscher2000 said

mwrr said

I found a "solution" somewhere else that said to reset (turn off then back on) "Enable application protocol filtering" in my eset NOD32 antivirus program. Since I did that, I've not received the error message.

That's an interesting tip! I started a discussion on the related help article: Secure connection failed and Firefox did not connect. If you would like to participate in the discussion -- since you have direct experience -- here's a link: https://support.mozilla.org/kb/secure.../7169.)

I added that tip to the Secure connection failed and Firefox did not connect KB article, along with a link to the http://www.askvg.com/fix-secure-connection-failed-problem-in-mozilla-firefox-web-browser/ AskVG article mentioned in the discussion thread.