How to connect local VSCode instance to VS Code HA Add-on via ssh?

eugene78 · February 2, 2024, 3:30pm

Happy to report that I’ve solved the issue by:

Launching my VS Code desktop version 1.86.0.
Downgrading the remote-ssh extension version to 0.107 from within VS Code.
Changing the ‘update mode’ setting to ‘none’ (will require a restart of VS Code).
Downloading and installing version 1.85.2 of vscode.

After following these steps, I’m now able to connect my desktop VS Code (1.85.2) to VS Code HA add-on via SSH, as I used to previously.

The underlying issue remains however: a dependency on some libraries on HA add-on’s side (minimum GLIBC >= 2.28 apparently from the comments in the GitHub issues) is preventing VS Code 1.86.0 from connecting successfully over SSH.
Hoping this issue will be fixed soon…

golocal · February 2, 2024, 3:48pm

amazing, @eugene78 ! Thanks for all the follow ups

mrhand · February 2, 2024, 6:00pm

Nice, can confirm that downgrading the versions gets it working again. I took a look at the github issues and currently they’re not planning to fix it but may have misjudged how widely used it is. Luckily someone developed a workaround script for the latest versions as well. First you’ll need to add some more packages to the SSH addon:

nodejs
npm
make
g++

With those installed, save the script in one of the mounted directories like /root/share, otherwise you’ll lose it when the container restarts. All I changed was the mynode variable to /usr/bin/node. After running the script to install the npm dependencies, remote ssh with vscode 1.86 is back in business.

Even better - the new versions allow you to silence that notification about not meeting all the prerequisites.

xiduis15 · February 2, 2024, 11:42pm

Thx a lot @eugene78 ! it’s work great for me

sammyke007 · February 3, 2024, 7:55am

Guys… Drop SSH and use this integration:

It fires up a Remote Tunnel (not Remote SSH) to connect to from your vscode or vscode.dev using your Github credentials. Works perfect! You do need to enable it after every HA restart… but hey… we’ve got automations for that

Some extra information:
Vscode Remote Tunnels

mrhand · February 3, 2024, 4:07pm

Interesting… the downside being that has to bounce through Azure instead of staying on the same LAN

nullae · February 3, 2024, 4:32pm

I too just ran into this issue, but I’m a bit green on doing command line stuff.

I can access root/share through HA File editor addon and create the file, can you tell me how to run it?

Given that we want this file not to be deleted, I assume we have to rerun it every reboot, or can that be automated?

mrhand · February 3, 2024, 4:56pm

The install goes to /root/.vscode-server, so that should stick around while you’re using the same container including after rebooting. I think the only time you’d need to re-run it is after upgrades to the SSH addon.

Looking again now, the easiest way to run it is probably to add it to the init_commands of the addon:

/bin/bash /root/share/vscodefix.sh

On my system that still takes about a minute to run after it’s already installed, so give it some time for npm to do its thing.

nullae · February 3, 2024, 5:22pm

~~That didn’t seem to work for me. Had to swap to YAML mode config as packages were failing to save and there was no field for init_commands but I think I have it right.~~

~~I can’t seem to spot anything interesting/related to the script in the addon logs either.~~

~~How would I go about just running this script manually for now, just throw it into the addons terminal?~~

Rebooted HA and VSCode seems to be up and running now. Cheers for the help!

eugene78 · February 7, 2024, 12:09pm

Hello, could you help me understand how using this integration would help solve the libraries issues?

The diagram on the VS Code Remote Tunnels page shows VS Code server running on the remote environment, which in my case would be my HA OS installation (installed in a VM on Proxmox).

How/why would this situation be different & better than my current configuration using the Advanced SSH & Web Terminal add-on?

Thanks for your clarifications.

sammyke007 · February 8, 2024, 7:44pm

It’s just easy to set up and it works with vscode.dev too (browser app / PWA). I’m not trying to sell it, just telling it’s working great and doesn’t require you to set up SSH access…

eugene78 · February 10, 2024, 1:55pm

Happy to report that VS Code 1.86.1 update that was released on Feb. 8th has solved the issue, enabling again to connect to HA instance over SSH.

How to install the upgrade:

Launch VS Code desktop version 1.85.2.
Go to Settings and change the “update mode” setting back to ‘default’. This will require a restart of VS Code.
After restarting VS Code, execute Code / Check for updates… (on Mac). This will download the 1.86.1 version and prompt another restart.
After restarting again, the “Remote - SSH” extension should prompt an update to version 0.108.0. Be sure to select “auto-update” for this extension.

Note Microsoft’s position here:

We have discussed this more in the VS Code team and we have decided to allow VS Code to connect to an OS that is not supported by VS Code (no support for glibc >= 2.28) for 12 more months .
We hope this will provide the needed time for you and your companies to migrate to newer Linux distributions.

So while the issue is solved in the short term, we still need a proper solution for the longer term.

Cheers!

kagehisa · April 17, 2024, 2:17pm

I recently tried to use the SSH extension as well with the latest VSCode and and latest HA updates. The VSCode remote Server seems to need a real ps command and not the alpine shipped busybox variant.
If anyone faces some issues and sees a ps related error in the log try adding the package procps to the packages section of the ssh and terminal extension.
This made it work for me.

mrhand · April 18, 2024, 4:18pm

Nice, procps fixed mine again too for 1.88

mikeodr · April 18, 2024, 6:48pm

Amazing, thanks so much. I was noticing ps was failing but didn’t realize it was busybox being the issue.

danandrea737 · April 22, 2024, 10:59am

Yass! Nice catch! I wasn’t able to catch that in the ssh output while trying to connect. Thanks!

Nexxado · April 26, 2024, 2:20pm

Same for me, the procps was the solution, full working config:

ssh:
  username: my_user
  password: ""
  authorized_keys:
    - my_key
  sftp: false
  compatibility_mode: false
  allow_agent_forwarding: false
  allow_remote_port_forwarding: true
  allow_tcp_forwarding: true
zsh: true
share_sessions: false
packages:
  - procps
init_commands: []

DBM · June 26, 2024, 11:11am

Adding procps helped me as well, thanks a million! My current config (as it differs from the one @Nexxado provided)

authorized_keys:
  - >-
    ssh-rsa
  password: ""
apks:
  - procps
server:
  tcp_forwarding: true
  sftp: false
  compatibility_mode: false
  allow_agent_forwarding: false
  allow_remote_port_forwarding: true
  allow_tcp_forwarding: true
zsh: true
share_sessions: false
init_commands: []

thargy · October 15, 2024, 9:32pm

Changing from packages to apks fixed it for me thanks!

David_Nagy · November 17, 2024, 5:32pm

HI All,

I was using the proposed setup:

ssh:
  username: xxx
  password: ""
  authorized_keys: xxx
  sftp: false
  compatibility_mode: false
  allow_agent_forwarding: false
  allow_remote_port_forwarding: true
  allow_tcp_forwarding: true
zsh: false
share_sessions: false
packages:
  - nodejs
  - npm
  - make
  - g++
init_commands: []

But at some point, most likely after some of the update, I am unable to edit through VS code.

Failed to save ‘!’: Unable to write file ‘vscode-remote://ssh-remote+192.168.x.1/root/config/xxx.yaml’ (NoPermissions (FileSystemError): Error: EACCES: permission

I did not change anything like for a year.