microsoft / microsoft/vscode-remote-release
Port Forwarding Missing
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Type: Bug
The steps to reproduce are just starting VScode and be connected to a remote tunnel. The ports tab is just gone.
The whole section for port forwarding is just gone. I've checked both the left side nav under remotes where it usually was and nothing. Same in the terminal area. Finally apparently there is supposed to be a command pallete command you can run to reveal it which also fails to do so.
EDIT
I noticed that the ports tab is specifically disappearing when connecting to a WSL2 target of a remote tunnel.
Extension version: 1.5.2
VS Code version: Code 1.103.1 (Universal) (360a4e4fd251bfce169a4ddf857c7d25d1ad40da, 2025-08-12T16:25:40.542Z)
OS version: Darwin x64 23.6.0
Modes:
Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300) |
| GPU Status | 2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 2, 2, 2 |
| Memory (System) | 16.00GB (0.01GB free) |
| Process Argv | --crash-reporter-id 3d3ec003-fddb-4a36-9524-eb31ec50c7e1 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: ATSDev (jfelicianiws) |
| OS | Linux x64 5.10.102.1-microsoft-standard-WSL2 |
| CPUs | Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8 x 0) |
| Memory (System) | 23.48GB (7.44GB free) |
| VM | 0% |
A/B Experiments
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
747dc170:31275177
aj953862:31281341
9d2cg352:31346308
convertlamdat:31368659
nesew2to5:31336538
agentclaude:31335814
nes-set-on:31340697
6abeh943:31336334
envsdeactivate2:31353495
0927b901:31350571
4gdec884:31348710
45650338:31358607
0cj2b977:31352657
gaj49834:31362110
newchatstate:31363049
gemagent1cf:31368470
retryenabled:31370050
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the missing Ports tab with VS Code 1.103.1 while connected through a remote tunnel to the reported WSL2 target. Check the Remote Development ports locations and the Command Palette command; done means port forwarding is visible in the expected locations and can be revealed through the command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, vscode
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100