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! 🎁

Search 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

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

  • 1 reply
  • 17 have this problem
  • 25 views
  • Last reply by 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

Chosen solution

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.


Read this answer in context 👍 2

All Replies (1)

more options

Chosen Solution

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.