VSCode Extension Gives Connection Error
When trying to connect to a workspace using the extension it gives the error on the image
65 Replies
<#1244292522339995769>
Category
Help needed
Product
Coder OSS (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
Here is the Output logs
the
kex_exchange_identification: Connection closed by remote host
means that the SSH connection was interrupted
which usually means some firewall is blocking it
do you have the Coder CLI installed on your machine ?no?
now I have the coder cli
you should login using
coder login <url>
then do coder ssh WebTask-Sujal
and show the outputusing terminal?
yes
does not work
oh yeah it didn't add it to the PATH
yeah
add
C:\Program Files\Coder\bin
to your PATHsystem or user?
it doesn't really matter in our case but you should do system since the install is system-wide anyways
good now
nice
thats the ssh output
the hosted coder is outdated?
yeah but that's not too bad usually
should I update it and try again?
not really, that's just a warning
the name i gave you was wrong
oh okay
try
coder ssh sujalgoel/WebTask-Sujal
you need to prefix with the user when the workspace is not yoursconnected
okay
can you try opening your SSH configuration file and showing the Coder section
you can do Ctrl+Shift+P and search "Open SSH Configuration" in VSCode
sure
okay
can you try running
ssh coder-vscode--sujalgoel--WebTask-Sujal -v
manually ?from vs code terminal?
from any terminal
here
hmm
can you log in to Coder again ?
by doing Ctrl+Shift+P and searching "Coder: login"
retry this command now ?
again
that's very weird
yeah
i am doing some testing
I can connect to mine
not others
Could you try running the following snippet in PowerShell ?
it does an API request to list workspaces with the session token configured in your Coder extension
I think the token generated with the extension does not have access to the workspace you're trying to access
my bad you're on insiders too
yes
retry the snippet now
i've edited it
so it does see it
yes
could you try this @Dãrķ Søŭł ?
whoops
again insiders
no this time i just forgot to replace the workspace name
try now
sorry wrong endpoint again
try now
i don't need the output as it can be sensitive
i just need to know if you're getting the logs
a lot of ids
yeah so it has permission to access those
yeah
i have a vague idea of what might be going on but I suspect this was patched in the latest version
could you update your coder deployent and retry ?
sure!
I will update the coder we host
@Dãrķ Søŭł closed the thread.