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!

ابحث في الدعم

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

Secure connection failed - SEC_ERROR_LIBRARY_FAILURE

  • 1 (رد واحد)
  • 0 have this problem
  • 1 view
  • آخر ردّ كتبه zeroknight

more options

I'm running Firefox 102.4.0 ESR (32 bit) on a Win-7 (32 bit) PC.

It works fine. I visit a LOT of websites, it works fine.

Until just now. I'm trying to bring up namecheap.com (a domain registrar) and I'm getting this message:

Secure Connection Failed An error occurred during a connection to www.namecheap.com. security library failure. Error code: SEC_ERROR_LIBRARY_FAILURE

I'm not given any option to alter any FF settings or to otherwise create an exception to "trust" this site to be able to access it.

I've read where changing security.pki.crlite_mode (currently 3) to something else (like 0) and I've tried that, and unless I have to close and restart FF for that to take effect (which I have not done) then that setting doesn't fix the issue.

What exactly is going on here? Why is only THAT SITE giving me problems?

I'm running Firefox 102.4.0 ESR (32 bit) on a Win-7 (32 bit) PC. It works fine. I visit a LOT of websites, it works fine. Until just now. I'm trying to bring up namecheap.com (a domain registrar) and I'm getting this message: Secure Connection Failed An error occurred during a connection to www.namecheap.com. security library failure. Error code: SEC_ERROR_LIBRARY_FAILURE I'm not given any option to alter any FF settings or to otherwise create an exception to "trust" this site to be able to access it. I've read where changing security.pki.crlite_mode (currently 3) to something else (like 0) and I've tried that, and unless I have to close and restart FF for that to take effect (which I have not done) then that setting doesn't fix the issue. What exactly is going on here? Why is only THAT SITE giving me problems?

All Replies (1)

more options

Why stuck on 102.4.0esr? You should be on 102.15.1esr or preferably 115.10.0esr which has the latest critical security patches.

I can access *namecheap.com* on 102.4.0esr.

In Connection Settings, try toggling "Enable DNS over HTTPS" on/off and change "Use system proxy settings" to "No proxy".

Does it still happen in Troubleshoot Mode?