Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

Outlook live blocked by Mozilla Firefox

  • 5 balas
  • 10 memiliki masalah ini
  • 255 kunjungan
  • Balasan terakhir oleh SquallLion1
  • Terselesaikan

"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

Solusi terpilih

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

Baca jawaban ini dalam konteks 👍 2

Semua Balasan (5)

Solusi Terpilih

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

thank you. i will.

no issue with Google Chrome. then, Firefox is guilty

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...