A few users have reported Coder workspaces being unreachable over Coder Connect after switching networks, or toggling another VPN on the system. Some of those users have also noticed the workspace state fail to update when this is the case (e.g. a yellow status when the workspace isn't running). Toggling Coder Connect off and on appears to consistently work around the issue.

The output fromlog stream --predicate 'processImagePath CONTAINS "com.coder.Coder-Desktop.Helper"' --info --debug whilst this is happening includes:

com.coder.Coder-Desktop.Helper: [com.coder.Coder-Desktop.daemon:vpn.net.wgengine] ping(fd7a:115c:a1e0:4fdd:810f:78f4:29dd:1b52): no matching peercom.coder.Coder-Desktop.Helper: [com.coder.Coder-Desktop.daemon:vpn.net.wgengine] open-conn-track: timeout opening (TCP [fd60:627a:a42b:41f4:9616:7b2a:3a8c:f11f]:61602 => [fd60:627a:a42b:4fdd:810f:78f4:29dd:1b52]:22); no associated peer node