Change:
remoteSocket.onClose(() => localSocket.destroy()); remoteSocket.onEnd(() => localSocket.end()); remoteSocket.onData(d => localSocket.write(d.buffer)); <ins> localSocket.on('data', d => remoteSocket.write(VSBuffer.wrap(d))); </ins> localSocket.resume(); }

Discussion:
Type: <bBug</bPort forwarding over ssh is not working using vscode-insiders. It is working using vscode. How to replicate: some http server on the remote the port to be forwarded and select http as a protocol opening in browser / doing a curl from your local machine the request is stuck pending VS Code version: Code - Insiders 1.82.0-insider (, 2023-08-21T05:32:43.957Z) OS version: WindowsNT x64 10.0. Modes: Remote OS version: Linux x64 6.1.38-59.109.amzn2023.x8664 <details<summarySystem Info</summary </details<details<summaryExtensions (54)</summaryExtensionVersion ------ Handlebars0.4.1 vsc-python-indent1.18.0 dotenv1.0.1 remote-containers0.305.0 remote-ssh0.105.1 remote-ssh-edit0.86.0 remote-wsl0.81.0 vscode-remote-extensionpack0.24.0 remote-explorer0.4.1 remote-server1.4.2 material-icon-theme4.29.0 indent-one-space1.0.0 vscode-todo-highlight1.0.5 nugetpackagemanagergui2.0.6 Handlebars0.4.1 vue-peek1.0.2 vscode-markdownlint0.51.0 vscode-eslint2.4.2 gitlens2023.8.1905 EditorConfig0.16.4 prettier-vscode10.1.0 vscode-jest-runner0.4.66 copilot1.104.347 copilot-chat0.7. vscode-github-actions0.26.1 todo-tree0.0.226 terraform2.27. vscode-test-explorer2.21.1 vscode-nuget-package-manager1.1.6 roslynator4.4.0 vsc-python-indent1.18.0 vscode-python-test-adapter0.7.1 dotenv1.0.1 vscode-scss0.10.0 vscode-docker1.26.0 csharp2.0.376 vscode-dotnet-runtime1.7.0 black-formatter2023.5. flake82023.7. isort2023.11. python2023.15.

vscode-pylance2023.8.31 test-adapter-converter0.1.8 indent-rainbow8.3.1 material-icon-theme4.29.0 prisma5.1.0 vscode-scss-formatter3.0.0 indent-one-space1.0.0 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 vscode-conventional-commits1.25.0 volar1.8.8 vscode-typescript-vue-plugin1.8.8 vscode-todo-highlight1.0.5 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
I can reproduce this with SSH, but not with Dev Containers. have there been any changes to SSH recently that might cause this?
Happened to me yesterday too. Spend a lot of time rebooting my machine and killing processes until I tried regular vscode to find that port forwarding was working fine there. What is weird though is that the browser just hangs. Nothing happens if you try localhost:4000. There is no error it just hangs but if I try a port that isn't being used like localhost:5000 then the browser says that there is a connection error
I can reproduce
I have tried the latest version And I still cannot connect to my react dev server using port forwarding into my ssh remote
I still have this issue in the latest version: To reproduce: node script . a request from client side: side receives only the first chunk: After this, the request gets stuck and never ends. In my case, the issue mostly affects small requests. A 10kb request always has the issue, but a 100kb request seems to be consistently fine. Size of the response also seems to be important. I connected to a distant server (with a ping of ~300 ms), but there doesn't seem to be any problem with the connection itself.
Fixed on the next Insiders. Good find, it was a latent issue that never got hit before. Root causing it was fun
Does this need to be verified with Remote-SSH specifically?
Yes, it requires remote SSH.

You can verify this issue and at the same time by following Dador's instructions
server: <img width="319" alt="image" src=""client: <img width="688" alt="image" src=""Looks verified in latest insiders
Sorry, it does not work for me. To reproduce: Repository at After starting the devcontainer on a remote ssh-host, launch task "Serve". Then access http://localhost:4000.
are you using the latest VS Code insiders?
Just updated:
I'm not able to reproduce that, and I doubt it's related to this issue since Containers does not use the code path in question.
So, different bug, same behaviour? It worked in insiders before, it still works in stable... it does not work anymore in the current insiders. Does that mean the next release will also no longer work? Edit: Just to make sure there's no misunderstanding: My devcontainer is running on a remote ssh server.
Most likely. Sharing any contents in the Console (from the "Developer: Toggle Developer Tools" command) and the "Shared" log from the Output panel would be useful in diagnosing the issue.
Preparing a new issue!