Closed rowandempster closed 1 year ago
Resolved with https://github.com/microsoft/vscode-remote-release/issues/6101 :
seemed to get it working with useLocalServer: false just once, and it now works without that setting.
Leaving this ticket open to address the issue which cause the need for useLocalServer: false
, or please update the documentation on https://goteleport.com/docs/server-access/guides/vscode/ to include this requirement.
What needs to be fixed:
VSCode uses ssh
command similar to this: ssh -v -T -D 58596 -o ConnectTimeout=15 node.example.com
. Currently, Teleport doesn't support -T
switch causing VSCode to fail. -D
flags seem to be supported in tsh, but not when using ssh
.
Lastly, ssh key forwarding is not implemented in Teleport ssh -A
. This feature is not needed to get the basic VSCode functionality, but VSCode also uses it in some cases.
Description
What happened:
Following the https://goteleport.com/docs/server-access/guides/vscode/ guide results in
Could not establish connection
from VSCode. Note thatssh
is working fine, meaning I can follow Step 1 of the guide, and dossh alice@node000.foo.example.com
.What you expected to happen:
A connection is successfully established and I am able to use the VSCode Remote - SSH extension. Note that I am able to use the VSCode Remote - SSH extension successfully with my own bastion I set up. But when I use the teleport proxy the connection fails, see the connection log below.
Reproduction Steps
Follow https://goteleport.com/docs/server-access/guides/vscode/
Server Details
teleport version
):Teleport v7.3.2 git:v7.3.2-0-gaa361fbc1 go1.16.2
/etc/os-release
):Client Details
tsh version
):Teleport v8.0.7 git:v8.0.7-0-geb8076446 go1.17.3
macOS
Debug Logs
Please let me know if you require this information to debug.
teleport --debug
)tsh --debug
)VSCode Connection Logs