SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT in FF Quantum 66.0.3
Dear Firefox community, with v66.0.3 on MacOS I suddenly can no longer load this page:
https://wiki.egi.eu/
With older versions I had no problem for that page and it still loads fine e.g. in Safari. It uses a certificate from a certificate authority that is fine for the intended audience of that service. The error page does not even give me an option e.g. to add an exception for that page, FF just refuses to go there (see image).
Giải pháp được chọn
Hi again, it similarly fails in Internet Explorer, i.e. the issue has nothing to do with Firefox. While my problem remains, we can at least close this matter, cheers! :-)
Đọc câu trả lời này trong ngữ cảnh 👍 0Tất cả các câu trả lời (4)
There is security software like Avast, Kaspersky, BitDefender and ESET that intercept secure connection certificates and send their own.
https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can
https://support.mozilla.org/en-US/kb/firefox-and-other-browsers-cant-load-websites
https://support.mozilla.org/en-US/kb/secure-connection-failed-error-message
https://support.mozilla.org/en-US/kb/connection-untrusted-error-message
Websites don't load - troubleshoot and fix error messages
No problems here with this website. The certificate is issued by TERENA SSL CA 3 -> DigiCert Assured ID Root CA
Try to disable IPv6 (check for other possible causes as well).
Được chỉnh sửa bởi cor-el vào
Hi all, thanks for the various suggestions! I now suspect there actually is a problem with the given site: I get the error only when I authenticate with my user certificate (which works fine for other, related sites demanding client authentication). Under those circumstances I also get the error now in a FF ESR 52.8.0 session on Linux, in which I still had the site open in another tab, i.e. it worked OK in that browser until recently. I have asked the site admins to look into what changed on their side...
Giải pháp được chọn
Hi again, it similarly fails in Internet Explorer, i.e. the issue has nothing to do with Firefox. While my problem remains, we can at least close this matter, cheers! :-)