Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

SSL Not Supported Error 29

  • 3 replies
  • 1 has this problem
  • 341 views
  • Last reply by FredMcD

user3670916
user3670916

Getting the above error message when I visit this site: https://publichealth.lacounty.gov/ Never had this problem before.

I have not been able to find a way to connect to it. Cleared cache and disabled all ssl, privacy, blocker settings I could think of, but nothing's worked. I'm on Win10 using FF 86.0.1. Someone else using Safari on a Mac was able to connect to the site no problem.

Attached is a screenshot of the message I get when trying to connect to the url. Thanks.

Getting the above error message when I visit this site: https://publichealth.lacounty.gov/ Never had this problem before. I have not been able to find a way to connect to it. Cleared cache and disabled all ssl, privacy, blocker settings I could think of, but nothing's worked. I'm on Win10 using FF 86.0.1. Someone else using Safari on a Mac was able to connect to the site no problem. Attached is a screenshot of the message I get when trying to connect to the url. Thanks.
Attached screenshots

Chosen solution

Thank you FredMcD.

I just did a test w my mac/chrome friend and they were able to reach the site no problem, while I had the same SSL block, so the problem is not limited to the site being down.

I did notice something this time: the mac/chrome combo indicated it wasn't a secure connection and upon inspection it was http. It was previously the case that my win10/ff combo would force an https connection, even if I manually typed in the url as http-only, but when I did that just now, I was able to connect to the public health site.

So it seems ff was still directing me to the (non-existent) https site. Having previously turned off ff's various protections, this time when I manually changed https to http in the address bar, I was able to successfully connect.

So I suppose I solved the riddle, largely of my own making, though I would say ff did have at least a little something to do w it.

Read this answer in context 👍 0

All Replies (3)

FredMcD
FredMcD

https://downforeveryoneorjustme.com/publichealth.lacounty.gov?proto=https

Publichealth.lacounty.gov Status Is publichealth.lacounty.gov down right now? It's not just you! publichealth.lacounty.gov is down.

user3670916
user3670916 Question owner

Chosen Solution

Thank you FredMcD.

I just did a test w my mac/chrome friend and they were able to reach the site no problem, while I had the same SSL block, so the problem is not limited to the site being down.

I did notice something this time: the mac/chrome combo indicated it wasn't a secure connection and upon inspection it was http. It was previously the case that my win10/ff combo would force an https connection, even if I manually typed in the url as http-only, but when I did that just now, I was able to connect to the public health site.

So it seems ff was still directing me to the (non-existent) https site. Having previously turned off ff's various protections, this time when I manually changed https to http in the address bar, I was able to successfully connect.

So I suppose I solved the riddle, largely of my own making, though I would say ff did have at least a little something to do w it.

FredMcD
FredMcD

That was very good work. Well Done.