Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

how can i restore a damaged certificate?

  • 1 odpowiedź
  • 3 osoby mają ten problem
  • 17 wyświetleń
  • Ostatnia odpowiedź od 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.

Wszystkie odpowiedzi (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.