X
Нажмите здесь, чтобы перейти на мобильную версию сайта.
Scheduled maintenance: Monday, March 30, between 3:30pm and 5:30pm UTC. This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn’t solve your issue and you want to ask a question, we have our support community waiting to help you at @firefox on Twitter

Форум поддержки

Firefox Updater invalid security certificate

Размещено

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!
Цитата

Дополнительные сведения о системе

Установленные плагины

  • Shockwave Flash 32.0 r0

Приложение

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

Дополнительная информация

cor-el
  • Top 10 Contributor
  • Moderator
17846 решений 161530 ответов
Размещено

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.

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.
Помогла ли вам это?
Цитата
Задать вопрос

Для ответа на сообщения вы должны войти в свою учётную запись. Пожалуйста, задайте новый вопрос, если у вас ещё нет учётной записи.