Unable to sign in and fetch rules behind proxy

[evelynluw]

Hello,

Environment: VSCode latest insider, using WSL for code repo

Version: 1.100.0-insider
Commit: 942d11fff1a3a4f0faa918b59803f699ec61b9b6
Date: 2025-04-16T05:03:47.938Z
Electron: 34.4.1
ElectronBuildId: 11317338
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

I am behind a corporate proxy URL, and I am not able to refresh the rules or log in with my proxy. Here are the console output from VSCode (obscured the ID):

Initializing server
Caching workspace targets
Finished caching workspace targets
Server initialized
Refreshing rules
[00.37][ERROR]: Unhandled message:
{
  "id": "8059a431-6e3d-xxxx-xxxx-xxxxxxxxxxxxx",
  "jsonrpc": "2.0",
  "result": null
}

And this is the result of setting semgrep.useJS to true:

Initializing server

Caching workspace targets

Finished caching workspace targets

Server initialized

Refreshing rules

Refused to set unsafe header "host"
Scanning single file

Scanned single file

Rules not loaded yet, not scanning anything.

Fatal error: Failed to download config from https://semgrep.dev/c/p/default, returned code 0: Error: Client network socket disconnected before secure TLS connection was established
    at TLSSocket.onConnectEnd (node:_tls_wrap:1730:19)
    at TLSSocket.emit (node:events:530:35)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

/home/xxxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:2149
throw err}function
^

Error: Fatal error: Failed to download config from https://semgrep.dev/c/p/default, returned code 0: Error: Client network socket disconnected before secure TLS connection was established
    at TLSSocket.onConnectEnd (node:_tls_wrap:1730:19)
    at TLSSocket.emit (node:events:530:35)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
    at /home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:307548:105
    at caml_call1 (/home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:2157:53)
    at /home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:6092:55
    at caml_call1 (/home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:2157:53)
    at aZjl (/home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:5940:3)
    at /home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:5943:166
    at q5 (/home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:5943:185)
    at /home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:5951:26
    at caml_call1 (/home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:2157:53)
    at q9 (/home/xxx/.vscode-server-insiders/extensions/semgrep.semgrep-1.10.3-linux-x64/dist/lspjs/Main.bc.js:5946:17)

Node.js v20.18.3
[Info  - 5:08:17 PM] Connection to server got closed. Server will restart.

Most likely this is due to proxy issues, however I have set those proxy settings in VSCode already:

    "http.proxy": "http://xxx.xxx.com:8000/",
    "http.proxySupport": "on",
    "http.proxyStrictSSL": false,

And I tested with a different extension "Network Proxy Test" and I was able to reach external URLs.

In my WSL, those environment variables are already set: http_proxy, https_proxy. Are there any variables I can set for semgrep to run behind a proxy?