Only Firefox desktop browser has: Error code: SEC_ERROR_REVOKED_CERTIFICATE
The Firefox desktop browser is the only one that give me this error Error code: SEC_ERROR_REVOKED_CERTIFICATE I am on a MAC OS using latest version of Mozilla Firefox desktop browser: 82.0.1 (64-bit) Incognito mode, cleared everything, reinstalled the browser and still got the same error. Talked with GoDaddy support and they told me everything is ok on their side. What is going on? Why: Safari, Chrome, Opera, Firefox Mobile (iOS) and so on have no problem loading my pages, but Firefox desktop has?
I looked on my GoDaddy hosting cPanel and the SSL are correctly generated and valid, so I don't understand what is going on with this browser.
Thank you! PS - If this is already answered, please point me to the correct reply.
Izbrana rešitev
I do not get this error in Firefox and there are no real problems reported.
Preberite ta odgovor v kontekstu 👍 0Vsi odgovori (4)
https://www.bing.com/search?q=SEC_ERROR_REVOKED_CERTIFICATE
‘ssl_error_rx_record_too_long’ or ‘cannot display the webpage’ Internet search; More often than not, you have something misconfigured!
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
I suggest asking GoDaddy to explain the following and do whatever is needed to make the test pass:
https://www.ssllabs.com/ssltest/analyze.html?d=resources.mini-box.com
Izbrana rešitev
I do not get this error in Firefox and there are no real problems reported.
Yes, the SSLLabs test originally retrieved a certificate issued October 13th but Firefox retrieves one issued October 20th. So perhaps there was a cache somewhere that still had the old one and it is clearing out over time.