VS Code Desktop - fails to activate extension
Hi everybody, a colleague and I are setting up coder in GCP.
We have a control plane VM and a docker VM that runs the containerized workspaces.
All is so far working very well, except for the VS Code Desktop button. When I click this, I get the relevant popup and upon clicking this vscode attempts to connect, but I get an error regarding hostname resolution.
I am able to connect to my workspace using the ssh connection from vscode.
Any pointers would be greatly appreciated
In the VS code devtools I see the following errors after trying to connect:
and
10 Replies
<#1276078439467585609>
Category
Help needed
Product
Coder OSS (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
hey, could you right click the "Open in VSCode" button and send its link here?
There is no option to copy any link from the button
Network tab of dev tools gives me this
vscode://coder.coder-remote/open?owner=jozef&workspace=testing-dbt-container&url=https%3A%2F%2Fcontrol-plane.coder.example.com%3A8443&token=CSDiBCHeq5-O9miiaeYXhO7sS2Ii0qKhN&openRecent=true&agent=main
I have changed the link address, as I don't want to provide the real one
If I try to connect via the coder remote vs code extension, I also have a problem, but if I create the host manually in the ssh config, using the link that is in the logs of the remote connection failure, it connects happily, but this is not optimal.
If I use Vs code insiders everything works perfectly from the coder remote extension.
However, this is no solution 😦
what URL are you accessing the Coder UI from?
replace <domain.tld> with example.com
Hi the domain for the coder ui is
https://control-plane.coder.example.com
hello, sorry for the delay
out of curiosity, why the control-plane subdomain?
could you screenshot these error messages so I can better understand the context?
Just something that my colleague set up prior to me onboarding to the team.
I might struggle doing this, as I have managed to get things working with my mac. However, I think my colleague still has these issues, so I'll try to post something back soon.
hey @jozef -- any luck?
Sorry, we're still working on cleanup of our overall tf code and we also plan to move to a new domain with new certs etc. I have the distinct feeling that once we apply all our planned changes, that things will simply start to function correctly.
alright, please let me know if you need anything :)