-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Could not establish connection to workspace-unique-name #7056
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
Comments
It seems that your token is invalid for some reasons. Could you try an advice from here: |
For reference, tried restarting, opening a workspace and then choosing to open in VSCode Desktop and got this error:
Will see what other approaches I might be able to test from the comment you mentioned. I don't however have a Mac Keychain as I am running in Linux. Just to be sure, I don’t need to download the Local Companion app as it is now automatically installed and executed, is that right? https://www.gitpod.io/blog/local-app Is it required to have a default ssh key in ~/.ssh/id_rsa? |
Some more notes. I was checking again the terminal and observed the mentioned ssh command. Tried to run it in a separate terminal windows and got the Too many authentication failures message indeed. And that probably might be explained because I have several ssh keys that are all probably being tried on so the server ends up rejecting it.
I have the following in my ~/.ssh/config but it doesn’t seem to make a difference at all:
Some more updates. After the connection failing (for not having IdentitiesOnly), manually editing the ssh config file and adding However it is very cumbersome to do this every time I want to open a workspace in VSCode Desktop. Waiting for it to fail, open the config file, add the line and reload the window of the remote connection. Any ideas @akosyakov? |
Correct, it is bundled with Gitpod extension.
Not, the local companion generates own config and key. What you explain makes sense https://superuser.com/questions/268776/how-do-i-configure-ssh-so-it-doesnt-try-all-the-identity-files-automatically if you have many identity files. I assume a fix is to add
|
@loujaybee could you share the full log if you face it again? 🙏 To make sure it's not related to desktop vscode settings like this issue microsoft/vscode-remote-release#6108 mentioned (as they have similar error message) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@dexslender Have you managed to resolve it? If not please follow https://www.gitpod.io/docs/help/troubleshooting#gitpod-logs-in-vs-code-browser-and-desktop EDIT: I checked your analytics. It seems you still have troubles with the same workspace always. Could you try to check whether it works with another repository? I wonder whether you have changed something that it can affect SSH server running in the workspace. EDIT: Also FYI we check overall system state and other users are successful connecting. SLO is over 99% EDIT: from peeking in backend logs I see that SSH server is failing to start. You can see supervisor.log under |
The server display this logs when connecting via VSCode
|
@dexslender Could you share a reproducible repo? Something is off public keys are missing in your workspace for |
@dexslender We identified a regression with non gitpod images and will deploy a fix shortly. |
Bug description
I am on Ubuntu 20.04.3 and I am not being able to use VS Code Desktop feature.
In VS Code Desktop I am receiving a "Could not establish connection to workspace-unique-name".
Steps to reproduce
Open a Gitpod workspace
Click "Gitpod" in the bottom left corner
Click "Gitpod: Open in VSCode"
Accept all prompts in VSCode side
Choose Linux when the following prompt appears

As soon as I choose it I receive the error:

Workspace affected
No response
Expected behavior
Gitpod and VS Code Desktop should work correctly.
Example repository
No response
Anything else?
The logs produced with remote login terminal open:
If it matters, I have tried to run it now again and got this:
The text was updated successfully, but these errors were encountered: