Updated W10 to FF 116 and had cert problems
After updating a W10 laptop from 115 to 116 of FF the user started having problems with getting to different websites (sites they worked on/with regularly). The problem is the cert DB. The doc I found says that it is cert8.db. Actually it is now cert9.DB.
What I had to do was go to task manager and kill a task that was holding the cert9.db file. Then I could rename it (cert9.old.db). Then restarted their laptop and FF came up and started fixing the cert file (as expected). This seems to have fixed their problem.
منتخب شدہ حل
If you run into this, you can't help but replicate it! All websites fail with some cert error or another. And several of them required login.... But I remember something about OV and some cert authority. Lost the note where I wrote that down.
As a result, I had to use my laptop to search the FF site for cert problems because I couldn't capture and email to me from the user's laptop.
The URL that caused me to see what the problem probably was is this: https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean#
This led me into finding a 12 year old solution. But it was specifically saying cert8.db. So I thought I should post something about this now being cert9.db and not cert8.db. That should help others realize it is the same problem/solution.
اس جواب کو سیاق و سباق میں پڑھیں 👍 0تمام جوابات (2)
Point of clarification: My system is W11 and it is the system where I posted this. The user's system is W10. The tag shows windows 11, and I can't seem to figure out how to fix that. I think this may be misleading.
منتخب شدہ حل
If you run into this, you can't help but replicate it! All websites fail with some cert error or another. And several of them required login.... But I remember something about OV and some cert authority. Lost the note where I wrote that down.
As a result, I had to use my laptop to search the FF site for cert problems because I couldn't capture and email to me from the user's laptop.
The URL that caused me to see what the problem probably was is this: https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean#
This led me into finding a 12 year old solution. But it was specifically saying cert8.db. So I thought I should post something about this now being cert9.db and not cert8.db. That should help others realize it is the same problem/solution.