We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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 @FirefoxSupport on Twitter and/r/firefox on Reddit.

Buscar en Ayuda

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

After installing 4.01, SSL doesnt work and an error appears: "could not read chrome manifest file"

  • 12 respuestas
  • 22 tienen este problema
  • 5 visitas
  • Última respuesta de cor-el

more options

After installing 4.01, SSL doesnt work and an error appears in the error Console: "could not read chrome manifest file". It shows path to supposed file (Apps/Firefox/Contents/MacOS/extensions/(972ce4...../chrome.manifest. But that file is not there, even in the preinstalled DMG package.

Mac Mini running 10.6. Have done clean reinstall twice, dumped cert8.db file. followed all Support suggestions. Two other Macs do not have this problem w 4.01.

Also MANY errors in Console during every non-SSL Google search, but it works

After installing 4.01, SSL doesnt work and an error appears in the error Console: "could not read chrome manifest file". It shows path to supposed file (Apps/Firefox/Contents/MacOS/extensions/(972ce4...../chrome.manifest. But that file is not there, even in the preinstalled DMG package. Mac Mini running 10.6. Have done clean reinstall twice, dumped cert8.db file. followed all Support suggestions. Two other Macs do not have this problem w 4.01. Also MANY errors in Console during every non-SSL Google search, but it works

Todas las respuestas (12)

more options

This issue can be caused by an extension that isn't working properly.

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

more options

Cor-el - Thank you for your response, but SAFE MODE did not help. I still cannot go to any https sites. The biggest problem is when I try to go to Firefox Add-ons Manager tab - it never populates with suggested Add-ons, because the URL is https.

In the Warnings window, it says "HTTP request failed for an unknown reason - Source file resource;//gre/modules/AddonUpdateChecker.jsm

But NO https site works, for example - https;//mail.google.com

more options

Cor-el - I also tried disabling all Plugins - this did not help. Also, the only extension is the DEFAULT one. Thank you very much for tyring to help resolve this.

more options

Cor-el - More trouble-shooting results with my Mac Mini. Reverting to Firefox 3.6 did NOT solve the problem (unable to connect to SSL sites). Also, other Macs running 4.01 also show the "could not read chrome manifest file" error, and yet they still do SSL fine. Therefore, it is not the new version of Firefox, or the chrome manifest warning. The problem is only that I cannot connect to SSL sites. There is no firewall that I know of, all encryption settings are as described in the "SSL disabled" support section.

The problem was noticed after upgrading to FF 4.01, but I also upgraded an Adobe Flash plugin at about that time, and also a Quicktime plugin. But the problem exists even when all plugins are disabled. So I am at a loss.

more options

Further troubleshooting. Creating a new profile and deleting the old one did not help, as suggested at:

https://support.mozilla.com/en-US/questions/669449

more options

Further troubleshooting. Reinstalling Snow Leopard and all updates to 10.6.7 did not help.

more options

We found that creating a new user account solved this issue.

more options

Samtarling and zzxc on Firefox chat support spent over an hour with me to resolve this problem. They are the greatest! So strange that nothing else other than creating a new user worked (and they had dozens of suggestions). Even stranger is that whatever was messed up in the old user account did not preclude Safari from SSL connections, only Firefox. But I am back up, and cannot say enough good things about Firefox and its free support folks!

more options

Did you try to reset the Keychain?

more options

cor-el: Just tried a keychain reset - it did not help. Fortunately, the "create a new user" suggestion from Samtarling and zzxc worked, so I have regained SSL access from the sick Mac. Thanks, Jack

more options

@jackvo - if you encounter this issue again, please get in contact. We're still unsure about what caused this problem.

more options

The error about the missing chrome.manifest is caused by the presence of the Default theme folder ({972ce4c6-7e08-4474-a285-3208198ce6fd}) that doesn't have such a chrome.manifest file.
The default classic/1.0 theme file is in the omni.jar archive.