搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

I am getting a warning that a secure connection failed but there is no way to bypass the warning.

  • 1 个回答
  • 1 人有此问题
  • 11 次查看
  • 最后回复者为 philipp

more options

In trying to logon on to Outlook for my email I am getting a warning message that the secure connction failed. It further says "An error occurred during a connection to outlook.live.com. Invalid OCSP signing certificate in OCSP response. Error code: SEC_ERROR_OCSP_INVALID_SIGNING_CERT". When I go to "Learn more..." and check on how to bypass it tells me to click on the Advanced button. But there is NO Advanced button that is clickable on any screen. I have had no problems logging in to my Outlook email until two days ago when this problem started. I also have no problem logging on to my Outlook email when I do so on a Samsung Galaxy S4.

In trying to logon on to Outlook for my email I am getting a warning message that the secure connction failed. It further says "An error occurred during a connection to outlook.live.com. Invalid OCSP signing certificate in OCSP response. Error code: SEC_ERROR_OCSP_INVALID_SIGNING_CERT". When I go to "Learn more..." and check on how to bypass it tells me to click on the Advanced button. But there is NO Advanced button that is clickable on any screen. I have had no problems logging in to my Outlook email until two days ago when this problem started. I also have no problem logging on to my Outlook email when I do so on a Samsung Galaxy S4.

所有回复 (1)

more options

hi, unfortunately MS has misconfigured a security feature (OCSP stapling) on their servers which got now cached in your local firefox installation.

in order to resolve that, please enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named security.ssl.enable_ocsp_stapling. double-click it and change its value to false - this will degrade a security feature in firefox, so please revisit it in a couple of days again after microsoft has fixed their stuff and turn it back on again then...