Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

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

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

Firefox Updater invalid security certificate

  • 1 reply
  • 1 has this problem
  • 2 views
  • Last reply by cor-el

Ken's Firefox
Ken's Firefox
more options

I rebooted my Windows computer and the automatic updater for Firefox started up, but my firewall blocked it because it said it had an invalid security certificate. I tried to allow it, but it again said I had an invalid certificate. I then blocked it, and it gave the same message. So I rebooted my computer again, and Firefox came up working properly, saying I had the newest Firefox version.

The firewall (via Norton Security) said there were less than 5 persons using this installer. That alone is weird.

What should I do the next time this happens? Thanks!

I rebooted my Windows computer and the automatic updater for Firefox started up, but my firewall blocked it because it said it had an invalid security certificate. I tried to allow it, but it again said I had an invalid certificate. I then blocked it, and it gave the same message. So I rebooted my computer again, and Firefox came up working properly, saying I had the newest Firefox version. The firewall (via Norton Security) said there were less than 5 persons using this installer. That alone is weird. What should I do the next time this happens? Thanks!

All Replies (1)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator
more options

It is possible that Firefox retrieved files via an open http connection that got upgraded to https causing this issue because the server doesn't have a proper certificate. Firefox will use a hash that is part of the update.xml files (retrieved via https) to verify that the file is correct, so it doesn't matter the http is used and not https.