-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscode desktop not working #288
Comments
Odd. Can you run the "Coder: Show Logs" command? |
it gives me no logs this output appears after canceling the ssh
|
Hmm, could you paste your SSH config file? |
|
Can you try adding additional |
Nah, I mean:
|
I tried that but everytime I click on vscode desktop, it gets overwritten and returns to its original shape |
Could you list for me the steps that I need to do locally on my laptop to be able to ssh from my local VSCode to the coder workspace ? after deploying the coder remotely on a cluster and creating the workspace maybe I missed something |
+1 |
my last ssh trial, it stops at debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1 and then nothing happens
|
Moving this to the |
@samar-elsayed That output looks like it is from running If Edit: you can also add |
@code-asher I tried to run ssh from the cmd to try to get some logs my logs are like the below
|
@samar-elsayed see if this works? |
I think the issue here is lookup coder.coder.svc.cluster.local: no such host |
I'm running coder on a bare metal Kubernetes cluster. I had the same issue re "lookup coder.coder.svc.cluster.local: no such host". Couldn't SSH into my workspace either. coder ping failed as well with the same "no such host" error. I managed to fix the issue by setting the CODER_ACCESS_URL in the values.yaml for the helm install to the service ip endpoitn issued by MetalLB. It seems the advice in the values.yaml on the kubernetes installation instructions
Isn't correct. Coder does need CODER_ACCESS_URL to be set for ssh connections to workspaces to resolve. |
Ah yeah it sounds confusing, maybe the comment means to say that only the dashboard will work? But either way yeah that comment needs to be improved I think. |
when I try to click on vscode desktop
nothing is happening and no proxy is used
The text was updated successfully, but these errors were encountered: