Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
The @google-cloud/secret-manager Node.js client fails silently when httpsproxy/httpproxy (or the uppercase variants) are set, requests through a proxy server never complete and no useful error is surfaced.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The proxy handling bug was in the underlying grpc-js library. Install @grpc/grpc-js@^1.0 (which includes the proxy fix) and pass it explicitly to the client: const grpc = require('@grpc/grpc-js'); const client = new SecretManagerServiceClient({ grpc }). Reporters confirmed this traverses the proxy correctly.
Source: https://github.com/googleapis/nodejs-secret-manager/issues/92
Shows how to fix google Secret Manager nodejs client fails silently behind https_proxy http_proxy. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes the Node.js @google-cloud/secret-manager client returning null from accessSecretVersion when the bluebird promise library is loaded.
Shows how to fix google Secret Manager PERMISSION_DENIED API has not been used in project wrong project number. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.