Re: [Firebase] Expired Certificate on firebaseapp.com still an issue??

[Michael Bleigh]

Hi PK,

We are unable to reproduce this issue and are unaware of any ongoing SSL expiration issues. There was an incident on February 13 but it was resolved the same day. Can you please follow up with Firebase support including details of the issue? We need the specific hostname having issues at a minimum, but ideally we'd also want to see all of the response headers of a failing response.

Thanks,

Michael Bleigh

On Mon, Feb 20, 2017 at 6:02 PM PK <p...@gae123.com> wrote:

I think I had seen this issue a couple of times in the past during development but attributed it to the dev. env., refreshed the browser and continued. 

Today I saw it on a customer site so it is real and super urgent. Basically, our web app that

uses the firebase javascript API in the background and otherwise works really well, was found stuck with the attached message. This is on Safari on an iPad running the latest iOS software. 

This is how we initialize the app:

firebase.initializeApp({
    apiKey: "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
    authDomain: "PROJECTNAME.firebaseapp.com",
    databaseURL: "https://PROJECTNAME.firebaseio.com"
});

This incident here mentions a similar issue as resolved but this happened this morning around 9:00AM PST

Thanks,

PK

www.gae123.com

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3b629b71-c363-4703-9a6b-09b4bd128c53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[PK]

Thanks Michael, I filed a support ticket. Since we restarted the app we have not seen the issue again. There are many other deployments; none has reported such an issue, yet again maybe they just restarted the app and did not bother to report an issue.

Has Firebase shared a postmortem on what happened and what will be done to make sure this does not happen again?

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANPY8KUdbmb-Xk%2Bkroux8qHfSbq5E9f%3DyC4ePwyzZ1P78i%2Bd1A%40mail.gmail.com.

[Michael Bleigh]

We don't have a public post-mortem, but here's a quick synopsis:

We recently completed a large-scale migration of our certificate infrastructure. At the end of the process, we overlooked a number of expired certificates that were still "active" in the system. Because our serving infrastructure does not differentiate between expired and non-expired certificates, on February 13 when the certs expired a number of sites were still serving them. We worked with our CDN partner to remove the expired certs from the system as quickly as possible which restored service.

In other words, it was a one-time disruption caused by an infrastructure migration and the conditions that led to it will not happen again.

Hope that helps clear things up.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/5D8EF5B7-5083-4B96-8B7C-ED76ADF5DF12%40gae123.com.