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

How do I reset firefox' trusted root CA list to default

  • 5 replies
  • 10 have this problem
  • 28 views
  • Last reply by sixthunder

more options

I took a look at the list of trusted root CAs and removed a couple of em in order to get rid of those that might get abused by untrusted governments (i.e. Germany, UK, USA) and apparently I also got rid of the CA trusts that are needed for checking for addon updates.

The problem is that firefox doesnt tell you which cert exactly it wants which makes this issue really hard to tackle (any ideas here?) The error console is really not verbose at all (is there a way for a verbose console?), since it only reports:

Warning: RDFItemUpdater:onError: There was an error loading the the update datasource for item {addon ID goes here}, error: nsIXMLHttpRequest channel unavailable

... numerous times.

So... since losing all my settings by starting a new profile is really not an option, how do I fix this?

I took a look at the list of trusted root CAs and removed a couple of em in order to get rid of those that might get abused by untrusted governments (i.e. Germany, UK, USA) and apparently I also got rid of the CA trusts that are needed for checking for addon updates. The problem is that firefox doesnt tell you which cert exactly it wants which makes this issue really hard to tackle (any ideas here?) The error console is really not verbose at all (is there a way for a verbose console?), since it only reports: Warning: RDFItemUpdater:onError: There was an error loading the the update datasource for item {addon ID goes here}, error: nsIXMLHttpRequest channel unavailable ... numerous times. So... since losing all my settings by starting a new profile is really not an option, how do I fix this?

All Replies (5)

more options

Rename (or delete) the file cert8.db (cert8.db.old) and secmode.db (secmode.db.old) in the Profile Folder

You can also delete the file cert_override.txt (cert_override.txt.old) in the Firefox Profile Folder if you have that file.


Help > Troubleshooting Information > Profile Directory: Open Containing Folder

more options

thanks, that did just what i was asking for in the headline. i still cant have FF searching for addon updates tho, so i guess the problem must be something else then :/

says:

Warning: RDFItemUpdater:onError: There was an error loading the the update datasource for item {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}, error: nsIXMLHttpRequest channel unavailable

for EVERY update its trying to find updates for. this error right here is from adblockplus, according to the ID anyhow

more options

Delete the files extensions.* (extensions.rdf, extensions.cache, extensions.ini, extensions.sqlite) and compatibility.ini in the Firefox profile folder to reset the extensions registry. New files will be created when required.

See "Corrupt extension files": http://kb.mozillazine.org/Unable_to_install_themes_or_extensions

If you see disabled, not compatible, extensions in "Tools > Add-ons > Extensions" then click the "Find Updates" button (in Firefox 4: right-click the extension -> "Find Updates") to do a compatibility check.

If it is related to ABP then you can try to ask in the ABP forum.

more options

i am able to install new addons without any issue. besides i temoporarilly moved those files to a diff folder but that did not chance my inability to update the addons from within firefox.

the ABP was just an example, im getting this error for ALL my installed addons

more options

I _may_ have found the root of the problem but if thats true, its not even a client-side issue at all.

so my idea was to use tamperdata (might have also used wireshark) to check, what FF is actually trying to do. turns out, FF tries to consult:

http://versioncheck.addons.mozilla.org/update/VersionCheck.php?<removed because not relevant>

turns out, that webserver is offline as in does not accept connections to port 80... so... is there an issue with the update server?