microsoft / microsoft/vscode-remote-release
remote ssh troubleshooting shows in terminal pane instead of default terminal on every start
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Type: Bug
At one point in the past, my remote computer went offline when connected to a Remtoe SSH session. Since then, every time I reconnect to that machine via Remote SSH in VS Code, the default terminal pane opens with a "Remote SSH Troubleshooting" dialog instead of the default temrinal. Every time I have to kill the terminal session and restart it in order to use the terminal.
Extension version: 0.117.0
VS Code version: Code 1.97.0 (33fc5a94a3f99ebe7087e8fe79fbe1d37a251016, 2025-02-04T22:41:26.688Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 5.15.167.4-microsoft-standard-WSL2
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8 x 2400) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 15.85GB (4.65GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | Container prosperlms-php (php) @ matt-work |
| OS | Linux x64 5.15.167.4-microsoft-standard-WSL2 |
| CPUs | Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz (4 x 0) |
| Memory (System) | 11.69GB (2.01GB free) |
| VM | 0% |
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
Start by reproducing the issue with the listed VS Code and Remote SSH versions in the reported Windows, WSL2, and container setup. Verify whether reconnecting after the remote machine goes offline opens the Remote SSH Troubleshooting dialog in the default terminal pane, and consider the issue done when a normal default terminal opens on every reconnect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100