Firebase authentication response 400: "auth/internal-error" "An internal error has occurred."

[nexusa...@googlemail.com]

Hi everyone,

currently, I am receiving a response 400 "An internal error has occurred." when trying to authenticate using email / password. Is anyone else facing this issue? 

I did not change my code which was running perfectly fine a few days ago. But now, authentication is not working anymore.

Additionally, I can see many anonymous user IDs (~190) - the app is still not productive but we only deployed a few files to hosting. 

Any idea what this could be? Really an internal issue with the authentication system or maybe the limits of the free plan might be reached?

Thanks and Regards

Andreas

[Bassam Ojeil]

Hey Andreas,

We have not heard any similar complaints recently.

Was this previously working for you? What is the environment you are running this from? Make sure you did not accidentally disable email/password providers in the console.

Also can you check your network console and report the full 400 response you are getting?

Bassam

[nexusa...@googlemail.com]

Hi Bassam, 

thanks for your reply. I just found some information, I missed at the first checks:

The general response, I can see in the console:

firebase.js:111 POST https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyPassword?key=AIzaSyB0Gv53LbgF6GmmZpeXwMHa93PvjfEPS0A 400 ()

code: "auth/internal-error", message: "An internal error has occurred."

However, if I check the JSON response, I can find: 

{

 "error": {

   "errors": [

     {

       "domain": "usageLimits",

       "reason": "keyExpired",

       "message": "Bad Request"

     }

   ],

   "code": 400,

   "message": "Bad Request"

 }

}

I don't get why our key is expired. It is the same as I can find when I click "add new web app" and the key was also working perfectly fine a few days back. Might this be related to the free usage plan? If so, a clearer description for that would be nice. At https://developers.google.com/youtube/v3/docs/core_errors#BAD_REQUEST I can only find: 

The API key provided in the request expired, which means the API server is unable to check the quota limit for the application making the request. Check the Google Developers Console for more information or to obtain a new key.

This seems to generic, if it is really related to the free usage plan. 

Thanks in advance

Andreas

[nexusa...@googlemail.com]

Hi Bassam,

in API Manager, I just found that the browser api key really expired on 29.06 and a new one was generated on 28.06. However, that key is not displayed in firebase when clicking "add new web app". I guess, this is a bug? Do you know why a new key was generated?

Thanks

Andreas

Am Samstag, 2. Juli 2016 04:05:39 UTC+2 schrieb Bassam Ojeil:

[Bassam Ojeil]

Hey Andreas, I am not sure why this is happening but I have notified the relevant parties regarding this. I do not believe this is related to this being a free feature. Did you migrate from an older Firebase v2 project, manually create the api key or did you have it automatically generated on a new Firebase project creation? 

Bassam

[nexusa...@googlemail.com]

Hey Bassam,

I tripledoubechecked, and see there - someone changed the key manually. Sorry, for the effort. However, I think we still can take some proposals out of that: 

- Expose google api error messages to the end user via firebase lib, instead of only displaying "internal error" 

- If possible, try to show the latest (updated) API key in firebase console, instead of only showing the first generated one 

Thanks a lot

Andreas