Firefox throws Secure Connection Failed for many Microsoft domains
-
As of May 29, Firefox users are currently unable to access some Microsoft websites.
When you try to connect select Microsoft owned domains such as Hotmail.com or Codeplex.com right now in Firefox, you may get a Secure Connection Failed error.
Sites that are affected by the issue include the following domains: hotmail.com, codeplex.com, visualstudio.com, azurewebsites.net, social.technet.microsoft.com, onedrive.live.com.
In fact, it appears that the majority of Microsoft owned domains are affected by the issue. Only some sites are not.
The error reads:
"Secure Connection Failed
An error occurred during a connection to xyz.codeplex.com. Invalid OCSP signing certificate in OCSP response. Error code: SEC_ERROR_OCSP_INVALID_SIGNING_CERT
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem."
When you try to load the site in another web browser, say Google Chrome or Internet Explorer, it loads fine and without any issues.
Temporary Workaround
The only option that Firefox users have right now to access affected Microsoft domains is to disable OSCP Stapling in the browser. Well, another option would be to use a different browser until the issue is resolved.
Type about:config in the address bar of Firefox and hit the Enter-key.
Confirm that you will be careful if the notification is displayed.
Search for the preference: security.ssl.enable_ocsp_stapling.
Double-click on it to set it to false.Doing so turns off OCSP Stapling in the Firefox web browser. Firefox will load the sites that refused to load before. A restart is not required.
Note: Disabling OCSP Stapling may affect the functionality of other websites that you visit, provided that they make use of the security feature.
http://technewsdir.com/firefox-throws-secure-connection-failed-for-many-microsoft-domains-fix
-
Thanks for this.
-
It looks like this issue has been resolved internally by Microsoft updating their certificates.
-
Had the same issue with Bing.com
-
holy schet for real
