Firebase hosting needs to re-verify *all* domains / hosting console not right?

[Ted McFadden]

Hi,

I've contacted support about this, but wanted to checking if anybody has also just received emails from firebase for all of their project hosting custom domains like this:

Please re-verify ownership of the domain [domain-name] connected to [hosting-name].
The previous verification for this domain has been lost. This can happen if you remove the site's verification DNS records from your domain provider, or if the user w\
ho completed the verification no longer has permission to add domains on the Firebase project. Allowed roles include Owner, Editor, and Develop Admin.

Email says we have 30 days to fix.

As far as I can tell our DNS entries for firebase as they were set some time ago and I am the owner of the project, so I am at a loss as what I am supposed to do here.

The Firebase Console Hosting view is not that helpful in this situation. Sporadically says "Unable to load domains" / [Try Again]. Clicking on "verify" to re-verify, shows an empty or just really large dialogue box with [Verify/Cancel] buttons. Verify immediately fails.

I can't get a look at what the DNS entries are expected to be for verify to succeed.

Any pointers would be appreciated.

Cheers,

Ted

[Sam Stern]

We are investigating this issue right now, clearly something went wrong. Right now you should do nothing, we currently believe most of these reverification emails are a mistake and the huge load of people trying to reverify is causing errors and resulting in some people having broken sites.

In the event that you truly do need to reverify after we fix this bug (which you probably don't) you'll still have 29 more days to do so, so no action required at this time.  We're doing everything we can to investigate and fix this, thank you for your patience!

- Sam

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/c3acf8d3-f929-406d-90e2-1bc5e9591d53n%40googlegroups.com.

[Ted McFadden]

Hi Sam,

Thanks for the update. I'll leave the console alone and call it a night. [Australia]

Cheers,

Ted

[Adrià Vilanova Martínez]

Thanks Sam!

I'd suggest updating https://status.firebase.google.com/ to indicate the current (partial) unavailability of the Firebase Console.

Cheers :-)

[Graham Dickinson]

Thanks for the info, Sam. I just received my email. 

Maybe the first step in fixing the bug should be to stop further emails going out? 

Krgrds, Graham

+27 84 798 6450

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAHafJBo6-Rj9Kvr0%3DfX7ey10C44xq-NFJUPa4ietfGNs2sMXhQ%40mail.gmail.com.

[Michael Bleigh]

Hi Graham,

Our email systems queue things up in advance so while we've stopped the ongoing process and are working to restore the affected records, some emails may still be delivered. In all cases no action is needed on your part and we will correct the issue on our end. Very sorry for the inconvenience, folks!

-Michael

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAKknc9B4GaSW%3DrCRuieiXYLcFyrSzs_AfvB4qn9A8UwbDKt4Ew%40mail.gmail.com.

[Graham Dickinson]

...further, I would hope that Google, just as quickly, sends out an email to each recipient of the erroneous one, explaining what happened and reassuring them that they should continue to use Firebase Hosting.

I am a startup and I need to be confident in my BaaS choice. Hope you understand my concerns. 

Krgrds, Graham

+27 84 798 6450

[Michael Bleigh]

Definitely understand the concern! We are focused right now on addressing the issue directly, but I'm also working on how we can communicate with affected users to let them know that things are actually okay.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAKknc9B5ZKunfBROh-cTSDb-Mhu7Q6eR8qqHkvb6NWHfCfYRjQ%40mail.gmail.com.

[Graham Dickinson]

Thanks, Michael. I appreciate your prompt response. :-) 

Krgrds, Graham

+27 84 798 6450

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANPY8KXuoUXjsgkbrDtzsVOoEgoNoORFKFfHy3PfFq%2B-4zpp6g%40mail.gmail.com.

[Graham Dickinson]

Thanks again, Michael. 

Krgrds, Graham

+27 84 798 6450

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANPY8KV5Ryf%3DLXipoPLApjQ4i2eoAto0iNX7_GCO8BTLE_AmNQ%40mail.gmail.com.

[Michael Bleigh]

To follow up on this thread, yesterday we sent a followup email to owners of all affected projects. Hopefully everyone on this thread who got the original email got the corrective.

Apologies again for the inconvenience, and thanks for being understanding!

Cheers,

Michael

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAKknc9AV5eeo2ZCs2AfdUF5%3DXGyMLzs%2B2_y%3DAnBNSDiY59ScRw%40mail.gmail.com.

[Graham Dickinson]

I got the follow up email, Michael. Thank you. 

Krgrds, Graham

+27 84 798 6450

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CANPY8KVqtGWtAXXZQv9BM4EMnen816qYY6m8gSQZq1kmmRggaw%40mail.gmail.com.

[michael griffith]

I also received the email that I needed to reverify my domains. I have been OOO and trying to catch up and after reading this thread it's unclear if I need to do anything.  

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAKknc9AMM9irA5SbOnvcDiQira5CXwgxz8B15FJtHHAhLbQqpQ%40mail.gmail.com.

[Sam Stern]

There's nothing you need to do, the incident has passed and your sites should not be affected!

- SAm

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAFhAot6pc9saHjP7zNARDgzigvxn%2B-8dsk9p%2BM3DSZLNvfCyeg%40mail.gmail.com.