microsoft / microsoft/vscode-remote-release
Unable to Connect via SSH for Agenst view
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing open issues and found none that apply.
- If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- I have read and performed the troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting - My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I did not ask the @remote-ssh participant for help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I did not try step 2 of the troubleshooting steps
Remote-SSH Log
Remote-SSH Log
2026-05-29 10:41:49.434 [info] [Shared] [SSHRemoteAgentHost] Connecting to ssh:<redacted>
2026-05-29 10:41:49.436 [info] [Shared] [SSHRemoteAgentHost] Built 2 auth attempt(s): agent, keyboard-interactive
2026-05-29 10:41:49.691 [error] [Shared] [SSHRemoteAgentHost] SSH connection error:
Expected Behavior
Connection via SSH for the agents view
Actual Behavior
I see a popup: Failed to connect via SSH to : AggregateError
Steps To Reproduce
- Open Agents-view
- selection the connection via SSh
- Failed to connect via SSH to : AggregateError
I do NOT have a remote-ssh log, but in shared I just see this 2026-05-29 10:41:49.691 [error] [Shared] [SSHRemoteAgentHost] SSH connection error: (this is not a failure in copying, there is no error)
Anything else?
No response
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 with the Agents view SSH connection flow and run Remote-SSH: Show Log to capture the complete diagnostic output. Follow troubleshooting wiki step 2 by running the generated SSH command verbatim outside VS Code. Done means reproducing the AggregateError and identifying the connection failure from actionable logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100