Firefox, SeaMonkey, PM Secure Connection Failed for many Microsoft domains

Discussion in 'other software & services' started by FanJ, May 30, 2017.

  1. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    4,632
    Firefox, SeaMonkey, PaleMoon Secure Connection Failed for many Microsoft domains.

    It is not only SeaMonkey (see this Wilders thread) that is giving this warning. That is why I start this new thread.

    There are many threads about it all over at the internet.
    I will give some links, but the problem is with Microsoft and they are working at it.

    First some links:

    gHacks:
    Firefox throws Secure Connection Failed for many Microsoft domains
    https://www.ghacks.net/2017/05/29/f...nnection-failed-for-select-microsoft-domains/

    DSLR Mozilla forum:
    [Pale Moon] Hotmail,Live,Outlook & Bing connection errors...NEWS re:Security
    https://www.dslreports.com/forum/r3...tlook-Bing-connection-errors-NEWS-re-Security

    Pale Moon forum:
    Hotmail, Live, Outlook and Bing connection errors, and our security.
    https://forum.palemoon.org/viewtopic.php?f=1&t=15823

    mozillaZine forum:
    Firefox blocking microsoft websites. Why?
    http://forums.mozillazine.org/viewtopic.php?f=38&t=3030714

    As I said, the problem is with Microsoft.
    Here is a statement by MS:
    https://portal.office.com/servicestatus

     
  2. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    162,650
    Location:
    Texas
    Thank you Jan. :thumb:
     
  3. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,193
    Location:
    Among the gum trees
  4. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    4,632
    You're most welcome, Ron !

    Here is an update from Microsoft:
    https://portal.office.com/servicestatus

    = begin quotes =

    Title: Can't load Outlook.com via Mozilla Firefox

    User Impact: Users may be unable to connect to Outlook.com via the Mozilla Firefox browser.

    More info: This is an incremental update to provide the latest status on the issue.

    Current status: We've completed restarting over 97 percent of the affected systems and we anticipate that impact will be remediated by 3:00 AM UTC on June 1, 2017. Users will continue to experience service restoration as the certificate data is refreshed across the environment. For complete details on this event, please reference the Restoring service post from 1:02 AM UTC on May 30th, 2017.

    Next update by: Wednesday, May 31, 2017, at 5:00 PM UTC

    = end quotes =
     
  5. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    4,632
    Update from Microsoft:
    https://portal.office.com/servicestatus

    = begin quote =

    Title: Can't load Outlook.com via Mozilla Firefox

    User Impact: Users may be unable to connect to Outlook.com via the Mozilla Firefox browser.

    More info: This is an incremental update to provide the latest status on the issue.

    Current status: We're now over 98 percent complete with our remediation actions and the vast majority of users should no longer be experiencing impact. We'll continue restarting the remaining systems throughout the day and we are confident that all systems will have the updated certificate installed by 3:00 AM UTC on June 1, 2017. At that time, we'll perform final testing and validation to confirm full remediation. For complete details on this event, please reference the Restoring service post from 1:02 AM UTC on May 30th, 2017.

    Next update by: Thursday, June 1, 2017, at 5:00 AM UTC

    = end quote =
     
  6. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    4,632
    Final update from Microsoft:
    https://portal.office.com/servicestatus

    = begin quote =

    Title: Can't load Outlook.com via Mozilla Firefox

    User Impact: Users may have been unable to connect to Outlook.com via the Mozilla Firefox browser.

    More info: Affected users may have seen the following error when using Mozilla Firefox to connect to Office 365 services: "Invalid OCSP signing certificate in OCSP response." While we were focused on resolving the issue, users could have connected to the affected sites via other browsers, such as Internet Explorer, Edge, Chrome, or Safari.

    Final status: We've completed our remediation actions and we've confirmed that impact is mitigated.

    Start time: Sunday, May 28, 2017, at 9:40 PM UTC

    End time: Thursday, June 1, 2017, at 3:00 AM UTC

    = end quote =
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.