dsh-wsl-net

Clash and V2Ray happily proxy your Windows browser traffic, yet the Node agent inside WSL still cannot reach the DeepSeek API or npm. The usual culprit is sneaky: Node 24 fetch silently ignores proxy environment variables unless NODE_USE_ENV_PROXY is turned on, and nobody noticed it was off.

The net_doctor tool in dsh-wsl-net lays the entire chain bare in one pass. It prints your HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY values with userinfo redacted, compares what the dsh web host process sees versus what the tool subprocess inherited, TCP-probes the configured proxy port to confirm it is actually listening, and then performs live HTTP checks against the DeepSeek API and the npm registry. When something is wrong, it does not just end with a log line. It hands you a ready-to-paste fix script that sets the missing variables or corrects the port, so the very next command works. It can also optionally inject NODE_USE_ENV_PROXY=1 and lowercase http_proxy aliases into subprocesses spawned for bash or npm, eliminating a whole class of "works in terminal, fails in tool" inconsistencies.

If you work day in and day out inside WSL, talking to DeepSeek or pulling npm packages through a Windows-side proxy client, this plugin is the thirty-second diagnostic that answers the question you always ask: who forgot to read the proxy? One tool call, one clear report, one paste-able fix. No API keys are ever printed, no Clash ports are mutated, and no proxy URL is invented out of thin air when none is configured.