Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

how can i restore a damaged certificate?

  • 1 freagra
  • 3 leis an bhfadhb seo
  • 17 views
  • Freagra is déanaí ó cor-el

more options

using "es file manager" , i moved all but the newest 'nightly build' , and i messed up "secure connection certificate" and now i get error code: sec_error_no_memory. i returned old 'nightly builds' , did not fix. tried to reinstall each build, still did not fix. uninstall nightly app, and tried to redownload and auto-updated it, still dose not fix damaged certificate, and i can't sign-in to my gmail account using foxfire v6 nightly build.

using "es file manager" , i moved all but the newest 'nightly build' , and i messed up "secure connection certificate" and now i get error code: sec_error_no_memory. i returned old 'nightly builds' , did not fix. tried to reinstall each build, still did not fix. uninstall nightly app, and tried to redownload and auto-updated it, still dose not fix damaged certificate, and i can't sign-in to my gmail account using foxfire v6 nightly build.

All Replies (1)

more options

Try to rename the cert8.db file in the Firefox profile folder to cert8.db.old or delete the cert8.db file to remove intermediate certificates that Firefox has stored.

If that helped to solve the problem then you can remove the renamed cert8.db.old file.
Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previous intermediate certificates.
Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.

If that didn't help then remove or rename secmod.db (secmod.db.old) as well.


Create a new profile as a test to check if your current profile is causing the problems.

See "Creating a profile":

If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.