microsoft / microsoft/vscode-remote-release

Unable to connect to external Linux Machine via SSH

Open
#11,347 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ssh
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.useLocalServer setting
  • 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 

[16:35:32.623] > Spawned remote CLI: 25977
[16:35:32.626] > Waiting for server log...
[16:35:32.661] > Waiting for server log...
[16:35:32.700] > Waiting for server log...
[16:35:32.741] > Waiting for server log...
[16:35:32.781] > Waiting for server log...
[16:35:32.823] > Waiting for server log...
[16:35:32.864] > Waiting for server log...
[16:35:32.906] > Waiting for server log...
[16:35:32.948] > Waiting for server log...
[16:35:32.990] > Waiting for server log...
[16:35:33.032] > Waiting for server log...
[16:35:33.074] > Waiting for server log...
[16:35:33.116] > Waiting for server log...
[16:35:33.158] > Waiting for server log...
[16:35:33.201] > Waiting for server log...
[16:35:33.243] > b1bd841ae79d: start
> listeningOn====
> osReleaseId==opensuse-slowroll==
> arch==x86_64==
> vscodeArch==x64==
> bitness==64==
> tmpDir==/run/user/1000==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> serverStartTime==621==
> execServerToken==aaaa1111-11a1-1a11-1111-1a1a1a1a1a11==
> platformDownloadPath==cli-alpine-x64==
> SSH_AUTH_SOCK====
[16:35:33.244] > DISPLAY====
> b1bd841ae79d: end
[16:35:33.244] Received install output: 
listeningOn====
osReleaseId==opensuse-slowroll==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==621==
execServerToken==aaaa1111-11a1-1a11-1111-1a1a1a1a1a11==
platformDownloadPath==cli-alpine-x64==
SSH_AUTH_SOCK====DISPLAY====
[16:35:33.248] Failed to parse remote port from server output
[16:35:33.248] Terminating local server
[16:35:33.250] Resolver error: Error
    at y.Create (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:744751)
    at t.handleInstallOutput (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:742832)
    at e (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:798600)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async /home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:823806
    at async t.withShowDetailsEvent (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:827501)
    at async /home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:795312
    at async P (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:793367)
    at async t.resolveWithLocalServer (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:794864)
    at async A (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:820659)
    at async t.resolve (/home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:824898)
    at async /home/fplinux/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:1113660
[16:35:33.266] ------

I tried deleting the code-<hash> binary downloaded in the remote machine, set port explicitly on the remote machine, there's no other logs nor any other tips have worked. I've noticed it tries connecting to a None port and a Local Server: Exit 15. I can login into the remote environment just fine using ssh so I know for a fact this is NOT an issue of my current ~/.ssh/config

You could at least learn how to do a god damn propper logging to tell the user wtf is going on and let them debug their end, Resolver error: Error is NOT proper logging.

So much telemetry and bloatware over monaco and for what? Typical "Microsoft" quality software, garbage to the end 🤦 absolute coding circus.

Expected Behavior

SSH working P.E.R.F.E.C.T.L.Y like it works when doing ssh fplinux@serverIP

Actual Behavior

No SSH, no login, just and endless loop of "Retry Connection" and "Read our stupid logs"

Steps To Reproduce
  1. Install OpenSUSE Slowroll (headless)
  2. Install Visual Studio Code via flatpak (or snap, tried both)
  3. Attempt to SSH into remtote OpenSUSE Machine
  4. Get stuck into an endless cycle of clowny messages
Anything else?

🤦 one has to wonder what kind of brainworm infested developers to make this the most used text editor.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Remote-SSH log and the generated extension.js stack location, then run the generated SSH command verbatim as requested by the troubleshooting wiki. Trace why the remote output has an empty listeningOn value and determine what diagnostic or connection behavior should result; done means the failure is reproducible and its cause is reported clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, vscode
Domain
devtools, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.