-
Notifications
You must be signed in to change notification settings - Fork 21
SSH config not modified on connection attempt #159
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
Thanks for opening this issue @aaronlehmann! Would it be possible for you to confirm that the permissions on
|
Interesting - we took another look and now see |
Seems related to #70 |
I attempted to reproduce this by clearing out my I did that a few times, alternating between closing VS Code normally and explicitly using |
Closing as we can't reproduce! |
Same issue. I set ssh config file path to log and configfile info
ls -lh .coder/config
-rwxrwxrwx 1 yy staff 0B Aug 5 12:02 .coder/config |
@lingdie Can you post the contents of Also if you could post the Coder extension log as well that would be awesome. |
@code-asher Coder extension log: The issue was resolved after I replaced the certificate. During the process, it can be observed that coder has very limited support for self-signed certificates. |
Glad to see it resolved! Yeah we do have a In this case it looks like the self-signed certificate was also malformed, I am not sure if |
A user of our Coder deployment encountered a problem where the VS Code plugin doesn't update
~/.ssh/config
with a# --- START CODER VSCODE ---
when clicking the link in the Coder UI to connect to a workspace, and therefore the connection fails.General logs:
"Coder" section of logs:
No value is set for "Config File" under "Remote.SSH":

The text was updated successfully, but these errors were encountered: