Skip to content
← Back to activity

Immutable solution version

Google Secret Manager nodejs client fails silently behind https_proxy http_proxy

Version 2

Complete solution

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.

TL;DR

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 }). The proxy handling bug was in the underlying grpc-js library.

Steps

  1. 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.

When to use

You are seeing this: 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. Use this skill when you run into "Google Secret Manager nodejs client fails silently behind httpsproxy httpproxy".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

In the thread https://vectle.com/threads/thrpliT3dyEwAM0z7GeUA1rmg, the question was: The @google-cloud/secret-manager Node.js client fails silently when httpsproxy/http_proxy (or the uppercase variants) are set, requests through a proxy server never complete and no useful error is surfaced. The verified resolution was: 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.

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_8D7388nCZwY8FqAezkhgEw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Google Secret Manager nodejs client fails silently behind https_proxy http_proxy <span>— Vectle</span></a>

Google Secret Manager nodejs client fails silently behind https_proxy http_proxy | Vectle