This article explains why you may see a Secure Connection Failed or a Did Not Connect: Potential Security Issue error page, and what you can do.
When a website that requires a secure (HTTPS) connection tries to secure communication with your computer, Firefox cross-checks this attempt to make sure that the website certificate and the connection method are actually secure. If Firefox cannot establish a secure connection, it will display a Secure Connection Failed or Did Not Connect: Potential Security Issue error page.
Secure Connection FailedA Secure Connection Failed error page will include a description of the error and a Try Again button. There is no option to add a security exception to bypass this type of error.
The error page will also include the following information:
Certain secure connection failures will result in a Did Not Connect: Potential Security Issue error page.
The error page will include a description of the potential security threat and an Advanced… button to view the error code and other technical details. There is no option to add a security exception to visit the website.
Website issues TLS version unsupportedSome websites try using outdated (no longer secure) Transport Layer Security (TLS) mechanisms in an attempt to secure your connection. Firefox protects you by preventing navigation to such sites if there is a problem in securely establishing a connection. Contact the owners of the website and ask them to update their TLS version to a version that is still current and secure.
The minimum TLS version allowed by default is TLS 1.2. Websites that don't support TLS version 1.2 or higher will display a Secure Connection Failed error page with a SSL_ERROR_UNSUPPORTED_VERSION error code and a message that says: This website might not support the TLS 1.2 protocol, which is the minimum version supported by Firefox. For more information, see this Mozilla blog post and Transport Layer Security (MDN Web Docs).
HSTS requiredOther websites may require HTTP Strict Transport Security (HSTS) and will not allow access with an insecure connection.
Security software conflictMany security products use a feature that intercepts secure connections by default. This can produce connection errors or warnings on secure websites. If you see secure connection errors on multiple secure websites, updating your security product or modifying its settings may resolve the issue. See this article section on Antivirus products for help with specific security products that can produce these errors, such as Avast, AVG and ESET software.
Alternatively, you can uninstall third-party security software and use Windows Defender, the built-in antivirus for Windows operating systems.
Incorrect system clockFirefox uses certificates on secure websites to ensure that your information is being sent to the intended recipient and can't be read by eavesdroppers. An incorrect system date can cause Firefox to detect that the website's security certificate is expired or invalid. Make sure your computer is set to the correct date, time and time zone. For more information, see How to troubleshoot time related errors on secure websites.
Other secure connection issuesFor a list and brief description of other secure connection errors, see NSS and SSL Error Codes in Firefox documentation.
These fine people helped write this article:
AliceWyman,
Bo102010,
philipp,
jscher2000 - Support Volunteer,
Underpass,
Tonnes,
Michele Rodaro,
Roland Tanglao,
Michael Verdi,
scoobidiver,
Swarnava Sengupta,
ideato,
user633449,
Mozinet,
Wesley Branton,
Lan,
Joni,
Artist,
mwrr,
YD,
Rashid,
Danny Colin,
PGGWriter,
Bithiah,
BD,
MR. Grey VolunteerGrow and share your expertise with others. Answer questions and improve our knowledge base.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3