From 7b38e395f4d5febfa4854b376b439c34420b4f23 Mon Sep 17 00:00:00 2001 From: Kurtis Mash <24705116+kurtismash@users.noreply.github.com> Date: Sat, 13 Dec 2025 02:41:52 +0000 Subject: [PATCH] Update remote proxy configuration VS Code 1.97.0 added the ability to use the local proxy configuration for remote extensions and enabled this by default. --- docs/devcontainers/containers.md | 1 - docs/remote/ssh.md | 1 - docs/remote/troubleshooting.md | 6 ++++++ docs/remote/wsl.md | 6 ++++++ 4 files changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/devcontainers/containers.md b/docs/devcontainers/containers.md index 3c15ff6123..734d9f27c5 100644 --- a/docs/devcontainers/containers.md +++ b/docs/devcontainers/containers.md @@ -597,7 +597,6 @@ From this point forward, the dotfiles repository will be used whenever a contain * The unofficial Ubuntu Docker **snap** package for Linux is **not** supported. Follow the [official Docker install instructions for your distribution](https://docs.docker.com/install/#supported-platforms). * Docker Toolbox on Windows is not supported. * If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either use an SSH key without a passphrase, clone using HTTPS, or run `git push` from the command line to work around the issue. -* Local proxy settings are not reused inside the container, which can prevent extensions from working unless the appropriate proxy information is configured (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information). * There is an incompatibility between OpenSSH versions on Windows when the ssh-agent runs with version <= 8.8 and the SSH client (on any platform) runs version >= 8.9. The workaround is to upgrade OpenSSH on Windows to 8.9 or later, either using winget or an installer from [Win32-OpenSSH/releases](https://github.com/PowerShell/Win32-OpenSSH/releases). (Note that `ssh-add -l` will work correctly, but `ssh ` will fail with `: Permission denied (publickey)`. This also affects Git when using SSH to connect to the repository.) See [here for a list of active issues](https://aka.ms/vscode-remote/containers/issues) related to Containers. diff --git a/docs/remote/ssh.md b/docs/remote/ssh.md index d8580597b3..56c8b5d9bf 100644 --- a/docs/remote/ssh.md +++ b/docs/remote/ssh.md @@ -286,7 +286,6 @@ SSHFS is the most convenient option and does not require any file sync'ing. Howe - Older (community supported) Linux distributions require workarounds to install the [needed prerequisites](/docs/remote/linux.md). - PuTTY is not supported on Windows. - If you clone a Git repository using SSH and your SSH key has a passphrase, VS Code's pull and sync features may hang when running remotely. Either use an SSH key without a passphrase, clone using HTTPS, or run `git push` from the command line to work around the issue. -- Local proxy settings are not reused on the remote host, which can prevent extensions from working unless the appropriate proxy information is configured on the remote host (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information). - See [here for a list of active issues](https://aka.ms/vscode-remote/ssh/issues) related to SSH. ### Container Tools Extension limitations diff --git a/docs/remote/troubleshooting.md b/docs/remote/troubleshooting.md index babd3e0017..abcd1db2b5 100644 --- a/docs/remote/troubleshooting.md +++ b/docs/remote/troubleshooting.md @@ -916,6 +916,12 @@ Extensions that access locally attached devices will be unable to connect to the **Resolution:** None currently. We are investigating the best approach to solve this problem. +### Extensions fail to connect to the internet when installed remotely + +Local proxy settings are reused on the remote host by default, which can prevent extensions from working. + +**Resolution:** Ensure that the remote host has connectivity to the internet and is configured with the appropriate proxy information (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information). Disable **Http: Use Local Proxy Configuration** in your VS Code [settings](/docs/configure/settings.md). + ## Questions and feedback ### Reporting issues diff --git a/docs/remote/wsl.md b/docs/remote/wsl.md index d6a9df5079..919266e676 100644 --- a/docs/remote/wsl.md +++ b/docs/remote/wsl.md @@ -262,6 +262,12 @@ When the remote VSCode is started from a WSL terminal, the download is done usin Once the server is up and running the proxy settings on the *Remote* tab are used. +### Extensions can't connect to the internet when installed remotely + +Local proxy settings are reused on the remote host by default, which can prevent extensions from working. + +**Resolution:** Ensure that WSL has connectivity to the internet and is configured with the appropriate proxy information (for example global `HTTP_PROXY` or `HTTPS_PROXY` environment variables with the appropriate proxy information). Disable **Http: Use Local Proxy Configuration** in your VS Code [settings](/docs/configure/settings.md). + ### Can I force an extension to run locally / remotely ? Extensions are typically designed and tested to either run locally or remotely, not both. However, if an extension supports it, you can force it to run in a particular location in your `settings.json` file.