Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Outlook live blocked by Mozilla Firefox

  • 5 ответов
  • 10 имеют эту проблему
  • 3 просмотра
  • Последний ответ от SquallLion1

more options

"Secure Connection Failed

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"

i can go thanks to Google Chrome

"Secure Connection Failed 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" i can go thanks to Google Chrome

Выбранное решение

hi SquallLion1, microsoft is currently having some issues with their server configuration - please try to reload the page a couple of times (by pressing F5) and see if it is loading then.

https://twitter.com/vcsjones

Прочитайте этот ответ в контексте 👍 2

Все ответы (5)

more options

Выбранное решение

hi SquallLion1, microsoft is currently having some issues with their server configuration - please try to reload the page a couple of times (by pressing F5) and see if it is loading then.

https://twitter.com/vcsjones

more options

thank you. i will.

more options

no issue with Google Chrome. then, Firefox is guilty

more options

apparently firefox is the only browser which checks for a valid OSCP stapling response for certificates on each secure connection.

in order to temporarily overwrite 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...