grpc connection fails on firestore/auth due to ssl bad signature errors #2609
Comments
|
We ran into a very similar-sounding issue with our gen2 nest js application. We are using auth guards to call |
Reproduced the issue with 12.1.1. |
|
Possibly related, upgrading from error message: errorInfo: {
code: 'auth/internal-error',
message: '//console.developers.google.com/iam-admin/iam/project?project=ida-ta and then retry. Propagation of the new permission may take a few minutes. Raw server response: "{"error":{"code":403,"message":"Caller does not have required permission to use project ida-ta. Grant the caller the roles/serviceusage.serviceUsageConsumer role, or a custom role with the serviceusage.services.use permission, by visiting https://console.developers.google.com/iam-admin/iam/project?project=ida-ta and then retry. Propagation of the new permission may take a few minutes.","errors":[{"message":"Caller does not have required permission to use project ida-ta. Grant the caller the roles/serviceusage.serviceUsageConsumer role, or a custom role with the serviceusage.services.use permission, by visiting https://console.developers.google.com/iam-admin/iam/project?project=ida-ta and then retry. Propagation of the new permission may take a few minutes.","domain":"global","reason":"forbidden"}],"status":"PERMISSION_DENIED","details":[{"@type":"type.googleapis.com/google.rpc.Help","links":[{"description":"Google developer console IAM admin","url":"https://console.developers.google.com/iam-admin/iam/project?project=ida-ta"}]},{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"USER_PROJECT_DENIED","domain":"googleapis.com","metadata":{"service":"identitytoolkit.googleapis.com","consumer":"projects/ida-ta"}}]}}"'
},
codePrefix: 'auth'reverting back to |
|
The I think what @asenmitrev reported is a different issue. @asenmitrev are you able to reproduce this issue in |
|
I also get a different error when using only auth, although the root cause still seems to be due to ssl failures. Including logs from an app using only token verification through firebase. Firebase version is at |
|
The issue was with any SSL connection through node, due to an old version of node. Upgrading to an LTS version of node (in my case 20.15.1) fixes the issue. Closing this issue. |
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
GRPC issues started happening randomly on a vps that was running firebase admin sdk on several different apps. The root cause seems to be a ssl error in openssl. I have included debug output from grpc running on one of the node apps. Running open ssl directly without going through node and grpc gives a successful handshake and valid certificate. I am trying to find the root cause of this, whether in grpc-js or in firebase admin sdk, as all other libraries in node do not have issues with ssl handshakes.
The issue occurs about 90% of the time, as sometimes firebase sdk is able to connect successfully, only to fail a few minutes later on subsequent requests to firestore or auth.
Important to note the same code runs successfully on other vps-s and on my local machine. This seems to be specific to this vps. Openssl and ca-certificates are at the latest version.
Relevant Code:
GRPC logs:
Output of
openssl s_client --connect firestore.googleapis.com:443The text was updated successfully, but these errors were encountered: