VSCode Code Catalyst Aws Toolkit Unable to Connect to Remote Dev Environment

0

I see another topic on this, but it seems a different case. Here is my log:

[13:55:00.021] Log Level: 1
[13:55:00.065] VS Code version: 1.80.0
[13:55:00.066] Remote-SSH version: remote-ssh@0.102.0
[13:55:00.066] win32 x64
[13:55:00.144] SSH Resolver called for "ssh-remote+XXXXXXXXXXXX", attempt 1
[13:55:00.146] "remote.SSH.useLocalServer": false
[13:55:00.147] "remote.SSH.showLoginTerminal": true
[13:55:00.147] "remote.SSH.remotePlatform": {"XXXXXXXXXXXX":"linux"}
[13:55:00.147] "remote.SSH.path": undefined
[13:55:00.148] "remote.SSH.configFile": undefined
[13:55:00.148] "remote.SSH.useFlock": true
[13:55:00.149] "remote.SSH.lockfilesInTmp": false
[13:55:00.149] "remote.SSH.localServerDownload": auto
[13:55:00.149] "remote.SSH.remoteServerListenOnSocket": false
[13:55:00.150] "remote.SSH.showLoginTerminal": true
[13:55:00.151] "remote.SSH.defaultExtensions": ["amazonwebservices.aws-toolkit-vscode"]
[13:55:00.151] "remote.SSH.loglevel": 1
[13:55:00.152] "remote.SSH.enableDynamicForwarding": true
[13:55:00.152] "remote.SSH.enableRemoteCommand": false
[13:55:00.153] "remote.SSH.serverPickPortsFromRange": {}
[13:55:00.153] "remote.SSH.serverInstallPath": {}
[13:55:00.167] SSH Resolver called for host: XXXXXXXXXXXX
[13:55:00.167] Setting up SSH remote "XXXXXXXXXXXX"
[13:55:00.175] Using commit id "660393deaaa6d1996740ff4880f1bad43768c814" and quality "stable" for server
[13:55:00.183] Install and start server if needed
[13:55:00.190] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V"
[13:55:00.199] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT
[13:55:00.200] Checking ssh with "C:\WINDOWS\ssh.exe -V"
[13:55:00.204] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT
[13:55:00.205] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V"
[13:55:00.208] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT
[13:55:00.209] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V"
[13:55:00.212] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT
[13:55:00.213] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V"
[13:55:00.323] > OpenSSH_for_Windows_8.1p1, Libr
[13:55:00.323] > eSSL 3.0.2

[13:55:00.340] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 65512 "XXXXXXXXXXXX" bash
[13:55:00.345] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[13:55:00.995] "install" terminal received data: "]0;C:\WINDOWS\System32\cmd.exe[?25h"
[13:55:00.996] Got some output, clearing connection timeout
[13:55:01.048] "install" terminal received data: "




























[?25h"

This stay blocked for hours saying: Setting up SSH Host XXXXXXXXXXXX: (details) Initializing VS Code Server

As suggested from Didier_AWS i try to run

ssh -v <MYAWSEVIRONMENT>

Here is the log

PS C:\Users\f8kibi> ssh -v MYDEVSERVER
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Reading configuration data C:\\Users\\f8kibi/.ssh/config
debug1: C:\\Users\\f8kibi/.ssh/config line 3: Applying options for MYDEVSERVER
debug1: Executing proxy command: exec "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -ExecutionPolicy RemoteSigned -File "c:\\Users\\f8kibi\\AppData\\Roaming\\Code\\User\\globalStorage\\amazonwebservices.aws-toolkit-vscode\\codecatalyst_connect.ps1" MYDEVSERVER
debug1: identity file C:\\Users\\f8kibi/.ssh/id_rsa type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\f8kibi/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: kex_exchange_identification: banner line 0: Test-Path : Impossibile associare l'argomento al parametro 'Path' perch\303\251 \303\250 null.
debug1: kex_exchange_identification: banner line 1: In C:\\Users\\f8kibi\\AppData\\Roaming\\Code\\User\\globalStorage\\amazonwebservices.aws-toolkit-vscode\\codecatalyst_connect.ps1:20 car:21
debug1: kex_exchange_identification: banner line 2: +     if (!(Test-Path $global:logFileLocation)) {
debug1: kex_exchange_identification: banner line 3: +                     ~~~~~~~~~~~~~~~~~~~~~~~
debug1: kex_exchange_identification: banner line 4:     + CategoryInfo          : InvalidData: (:) [Test-Path], ParameterBindingValidationException
debug1: kex_exchange_identification: banner line 5:     + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.TestPathCommand
debug1: kex_exchange_identification: banner line 6:
[...]
debug1: kex_exchange_identification: banner line 128:
debug1: kex_exchange_identification: banner line 129: Starting session with SessionId:

Unfortunatly I cannot understung the error, all ends on:

Starting session with SessionId

f8kibi
asked 10 months ago372 views
1 Answer
1

Hi, you should open a WIndows terminal and try to ssh -v (or -vv or -vvvv) your XXXXXXXXXXXX from this terminal to see if you can open the tcp session from your laptop to the remote machine or not. It will be easier to debug via ssh in terminal than via CodeCatalyst.

When you get the session via ssh in terminal, then you'll should be able to do same via CodeCatalyst: there may be some security group blocking your access from somwhere.

Hope it helps!

Didier

profile pictureAWS
EXPERT
answered 10 months ago
  • Thanks for your reply, I have may be some more useful information, but still dont know how to fix. I've updated the question.

    Thanks

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions