[BUG] - Remote SSH "Not an Authority"

[TheTaylorLee]

Environment/version

• Extension version: 12.7.0
• VSCode version: 1.80.0
• OS version: Windows 11

Error Shown

Steps to reproduce

1. Use project manager to open a remote SSH workspace

• Workspace Config

  {
  "folders": [
      {
          "name": "docker",
          "uri": "vscode-remote://ssh-remote+root@192.168.2.20/home/taylor/docker/appdata"
      },
      {
          "name": "dockerssd",
          "uri": "vscode-remote://ssh-remote+root@192.168.2.20/media/ssd/docker/appdata"
      },
      {
          "name": "github",
          "uri": "vscode-remote://ssh-remote+root@192.168.2.20/home/taylor/github"
      }
  ],
  "remoteAuthority": "ssh-remote+root@192.168.2.20",
  "settings": {
  },
  }

[alefragnani]

Hi @TheTaylorLee ,

Could you detail how the workspace is stored in Project Manager extension? I mean, is it something like:

        {
        "name": "My SSH Workspace",
        "rootPath": "~/Documents/Projects/MySSHConnection.code-workspace",
        "paths": [],
        "tags": [],
        "enabled": true,
        "profile": ""
    },

The extension doesn't do any connection to the remote machine, but only asks VS Code to open to path/workspace/folder you did configure in rootPath property. So, if it says something about authority when you open that workspace, I suppose it would do the same if you open the workspace via VS Code itself, using the native File / Open... command.

Hope this helps

[TheTaylorLee]

Thanks for the help. I tested opening the workspace directly and had the same issue. Seems like a bug with the new release of vscode.

{
        "name": "TALDocker",
        "rootPath": "g:\\github\\scripts\\VSCode\\Workspaces\\TALDocker.code-workspace",
        "paths": [],
        "tags": [],
        "enabled": true
}

[TheTaylorLee]

For anyone running into this I found some error logs in the Terminal > Window output. It indicated that vscode doesn't trust the path and is causing remote ssh connections to fail.

It's related to these changes by Microsoft.

https://github.com/microsoft/vscode/issues/182055

[alefragnani]

Thanks for pointing out the original VS Code issue. It can help other users for sure 👍

[TheTaylorLee]

Previous provided issue was incorrect and based off other issues referencing similar logs.

https://github.com/microsoft/vscode/issues/187202

SSH was not considered during a change to remote authorities code base in VS Code. Fix supposedly has been pushed to insiders and hopefully will be in the next stable vs code release.