Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i Support

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.

Læs mere

website www.msn.com does not support encryption. How do I fix this?

  • 3 svar
  • 3 har dette problem
  • 3 visninger
  • Seneste svar af cor-el

more options

I can open MSN but upper left corner is telling me site is not secure and private. That lock symbol is gone. Opened site info icon for security but how do i fix. Thank you for any help

I can open MSN but upper left corner is telling me site is not secure and private. That lock symbol is gone. Opened site info icon for security but how do i fix. Thank you for any help

Alle svar (3)

more options

Hi

I tried to open the site as https://www.msn.com (note the https) and received an error message relating to Microsoft has mis-configuring 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) and 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.

more options

Hi Before I could even attempt your suggestion, I opened it and added the https:// and it opened fine with the lock icon and it is now saying connection secure. Could Microsoft have fixed it ?? Thanks for your help

more options

Microsoft needs to reboot or update all servers that have cached this expired certificate that is used to sign the OCSP response, so if you no longer experiencing this issue then the server that you used is probably fixed.