Unable to connect to workspace | access to terminal, code-server, ssh not working. No matching peer
Have opened an issue for the same - https://github.com/coder/coder/issues/14598
Any suggestions? Please find the details of the issue below -
Hi,
I did a POC on my local machine and was able to setup a coder platform using docker compose specs. Now am try to set it up in corporate environment so that my team can evaluate it for our use cases.
However, when I try to do in corporate environment, am unable to access the workspace container. I tried using this docker-compose spec docker-compose.yml and also tried it do with the specs mentioned in the offline deployment section. Both these methods work on my personal desktop.
However, am encountering the same error - ping(unable to find peer) in both scenarios in corporate environment. I tried running coder ping -v <workspace_name> from remote-host, client machine, from inside the containers... and all of them give the same error.
Am thinking that this is some networking error but not sure what it is. Are there any specific ports that I have to open?
Am not able to connect to my workspace containers. Any help would be appreciated.
Below are the screenshots for reference -
GitHub
Unable to connect to workspace | access to terminal / code-server ...
Hi, I did a POC on my local machine and was able to setup a coder platform using docker compose specs. Now am try to set it up in corporate environment so that my team can evaluate it for our use c...
19 Replies
<#1281871794755731476>
Category
Help needed
Product
Coder OSS (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
have pasted them as a screenshot
hey @r1234, could you send a screenshot of the "DERP" section of the
/health page?
by the way, I have closed your GH issue so that we can focus our efforts in the Discord
hi.. thanks for the responding. Please find the screenshot below
I notice that my local deployment (the one that works) has OSHasIPv6 (green) but my corporate deployment ( not working ) has OSHasIPv6 (red)
are there any know ways of debugging connectivity with the workspace containers that we spin. I see I cannot do ssh | access its terminal | code-server etc.
@Phorcys - any help would be appreciated. if I hit a debug/health endpoint... I don't see any errors... but the ping just doesn't work...
is there any way to know which ports and which endpoints are being used for ping the operation from the client to workspace container .... all the intermediate ones... maybe that could get me somewhere.
alright, so to explain
Coder uses Tailscale between clients and the Coder workspaces
I do think it also uses it to communicate between workspaces and the control plane but don't quote me on that as I am not sure
in your case, all this being blocked basically means it can't communicate via DERP, but it should fallback to websocket
you are saying you are not able to connect to your workspaces, could you tell me how you are trying to access them and what error messages do you have (if any?)
anyways, the ping errors in your Coder logs are related to DERP, I suspect that your firewall blocks ICMP packets
maybe our networking requirements can help
Workspaces communicate to Coder using the provider
ACCESS_URL, also make sure that your workspaces can reach itIf my host, client and agents are on the same machine … then also am getting this error of now peer found
Is there any way to troubleshoot this ping error. I mean any command that I can run via cli to reproduce it… or something
I think it has to do with wgengine - am assuming that means wireguard coordinator
I see admin-v1-main have node field populated in my local setup
but it is nil in my setup in office
I think that might be the reason that it is not able to find peer
not sure what is causing the issue though and how to fix it
@r1234 some of us are at Open Source Summit EU atm so the answers will likely be delayed a bit
will get back to you next week if no one has picked it up :)
Thanks. Will ping you next week
sounds good!
just flying by, but even though it should fall back to WebSockets, you can force it
https://coder.com/docs/reference/cli/server#--derp-force-websockets
