Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

have recieved this - can you help please?

more options

bold text this was to connect to my homepage-BBc.co.uk/news

Secure connection failed and Firefox did not connect

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. Table of Contents

   Secure connection cannot be established
       Secure Connection Failed
       Did Not Connect: Potential Security Issue
   Website issues
       TLS version unsupported
       HSTS required
   Security software conflict
   Incorrect system clock
   Other secure connection issues

Secure connection cannot be established

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 an error page. Secure Connection Failed

A Secure Connection Failed error page will include a description of the error, an option to report the error to Mozilla 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:

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem.

Did Not Connect: Potential Security Issue

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, an option to report the error to Mozilla 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 unsupported

Some 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 still secure.

Starting in Firefox version 74, 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 Error code: SSL_ERROR_UNSUPPORTED_VERSION and a message that This website might not support the TLS 1.2 protocol, which is the minimum version supported by Firefox. The error page may also include a button, Enable TLS 1.0 and 1.1 that will allow you to override the minimum TLS requirement; however, Mozilla plans to remove this option and permanently disable TLS 1.0 and 1.1 in a future version of Firefox. HSTS required

Other websites may require HTTP Strict Transport Security (HSTS) and will not allow access with an insecure connection. Security software conflict

Many 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.

Alternatively, you can uninstall third-party security software and use Windows Defender, the built-in antivirus on Windows 8 and Windows 10.

Incorrect system clock

Firefox 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.

'''bold text''' this was to connect to my homepage-BBc.co.uk/news Secure connection failed and Firefox did not connect 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. Table of Contents Secure connection cannot be established Secure Connection Failed Did Not Connect: Potential Security Issue Website issues TLS version unsupported HSTS required Security software conflict Incorrect system clock Other secure connection issues Secure connection cannot be established 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 an error page. Secure Connection Failed A Secure Connection Failed error page will include a description of the error, an option to report the error to Mozilla 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: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Did Not Connect: Potential Security Issue 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, an option to report the error to Mozilla 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 unsupported Some 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 still secure. Starting in Firefox version 74, 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 Error code: SSL_ERROR_UNSUPPORTED_VERSION and a message that This website might not support the TLS 1.2 protocol, which is the minimum version supported by Firefox. The error page may also include a button, Enable TLS 1.0 and 1.1 that will allow you to override the minimum TLS requirement; however, Mozilla plans to remove this option and permanently disable TLS 1.0 and 1.1 in a future version of Firefox. HSTS required Other websites may require HTTP Strict Transport Security (HSTS) and will not allow access with an insecure connection. Security software conflict Many 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. Alternatively, you can uninstall third-party security software and use Windows Defender, the built-in antivirus on Windows 8 and Windows 10. Incorrect system clock Firefox 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.

Todas as respostas (2)

more options

What if you include the www --

https://www.bbc.com/news

-- does that make any difference? If so, you can update your home page address to the working address. See: How to set the home page.

more options

Actually, if you are in the U.K., I'm not sure whether it is meant to switch to the .com site for you. Hmm...