I have cloud functions running for months and suddenly all functions that rely on firebase authentication hit this error:
'Error while making request: getaddrinfo EAI_AGAIN identitytoolkit.googleapis.com identitytoolkit.googleapis.com:443. Error code: EAI_AGAIN'
My firebase is on Blaze (pay) plan.
Redeploying the functions also fail with this message:
Function deployment failed due to a health check failure. This usually indicates that your code was built successfully but failed during a test execution. Examine the logs to determine the cause. Try deploying again in a few minutes if it appears to be transient.
I would like to know if there is a resolution. Thank you!
DETAILS
I am also experiencing this issue, (although I don't use Firebase, I use Google Cloud Platform, and a Node app running on Google Cloud's "App Engine").
I called Google Cloud support and they acknowledged there was some issue; no ETA or workaround yet. Google Cloud support said they would email me a link where I can check status of the issue; I'll post here when I have it. Here is the general link to Google Cloud Status dashboard, note the specific Google Cloud issue #20007 likely affecting us this morning, in us-central1 region; their page doesn't mention EAI_AGAIN errors, but I bet those are related (and maybe affecting Firebase too)

(I tried workarounds like increasing process.env.UV_THREADPOOL_SIZE, but it didn't work -- this issue just started affecting our apps this morning, and our apps do not make "many requests" (i.e. that I should queue the the requests), our app only makes a few requests -- so I haven't tried queueing yet)
EDIT 10/6/2020 9:17AM PST
Looks like the issue is resolved as of 9:17AM PST, my Google Cloud app is able to make an outbound request without EAI_AGAIN Issues. Thanks, @JoeLeung and @singhnikhil.

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With