Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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.

Specific https:/ page will not load after udate to 38.05

  • 1 resposta
  • 17 têm este problema
  • 25 visualizações
  • Última resposta de cor-el

more options

https://my.albertahealthservices.ca will not load after update to 38.05 on my desktop.

I tried it on my laptop and it would load BUT after being undated to 38.05 it also failed to load this page.

Other secure pages (bank) load OK

Works OK in Chrome and IE

Error message: Secure Connection Failed

The connection to my.albertahealthservices.ca was interrupted while the page was loading.

   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.

Thanks Brian

https://my.albertahealthservices.ca will not load after update to 38.05 on my desktop. I tried it on my laptop and it would load BUT after being undated to 38.05 it also failed to load this page. Other secure pages (bank) load OK Works OK in Chrome and IE Error message: Secure Connection Failed The connection to my.albertahealthservices.ca was interrupted while the page was loading. 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. Thanks Brian

Solução escolhida

The website may try to fallback to a lower TLS version in a way that is no longer allowed in current releases or may be using a deprecated cipher suite.

You can open the about:config page via the location/address bar and use its search bar to locate this pref:

  • security.tls.insecure_fallback_hosts

You can double-click the line to modify the pref and add the full domain (my.albertahealthservices.ca) to the value of this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). There should only be domains separated by a comma in the Value column (example.com,www.example.com).

If this helps then you can contact this website and ask them to look into this and update their security.


Ler esta resposta 👍 2

Todas as respostas (1)

more options

Solução escolhida

The website may try to fallback to a lower TLS version in a way that is no longer allowed in current releases or may be using a deprecated cipher suite.

You can open the about:config page via the location/address bar and use its search bar to locate this pref:

  • security.tls.insecure_fallback_hosts

You can double-click the line to modify the pref and add the full domain (my.albertahealthservices.ca) to the value of this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). There should only be domains separated by a comma in the Value column (example.com,www.example.com).

If this helps then you can contact this website and ask them to look into this and update their security.