firebase-tools: Errors deploying functions: Server Error. Client network socket disconnected before secure TLS connection was established
[REQUIRED] Environment info
firebase-tools: 9.1.0
Platform: macOS 10.15.7 (catalina)
[REQUIRED] Test case
Attempt to deploy a firebase project that has hosting, functions, firestore
[REQUIRED] Steps to reproduce
firebase deploy
[REQUIRED] Expected behavior
Deploys correctly
[REQUIRED] Actual behavior
Fails with different error messages, mostly like
⚠ functions[onCreateUser3(us-central1)]: Deployment error. Server Error. Client network socket disconnected before secure TLS connection was established
Also saw: Error: Failed to get status of functions deployments
I spent over an hour resetting my internet connection (modem), connecting via ethernet instead of wifi, etc. Eventually I tried downgrading from firebase-tools 9.1.0 to 8.16.2 and it instantly fixed the problem – after over 10 failures with 9.1.0
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (8 by maintainers)
Hey all. I am getting a similar issue from within an app running in production on Cloud Functions. In production, I am using the bountyrush library for interacting with Firestore rather than the Firebase library. When running simple queries, I sometimes get the following error:
request to https://firestore.googleapis.com/v1/projects/[projectname]/databases/(default)/documents:runQuery failed, reason: Client network socket disconnected before secure TLS connection was establishedThe fact that this error occurs from within the Cloud Functions environment would seem to indicate (to me, anyway) that it’s not necessarily anything peculiar to your development environment.If I keep seeing these errors, I may have to stop using the bountyrush library, even though I suspect that the fault lies with the Firestore API, not the bountyrush lib itself.
@xaphod I’m inclined to agree with you because I’ve had more network issues with firebase-tools than other things on my personal computer although I have absolutely no idea where to begin this investigation. As you could imagine this could be anything from a Node library issue to something deep in Google’s network stack and most of us here on the CLI repo are wholly unqualified to investigate anything in the latter category.