Skip to content

When connecting to a Coder server behind a different VPN, workspaces are inaccessible #147

Open
@deansheather

Description

@deansheather

When using another VPN like a corporate VPN (e.g. Tailscale, tested with exit nodes enabled) or a consumer VPN (e.g. Mullvad) to access Coder, workspaces stay "yellow" and are unreachable.

It seems that the Coder Desktop VPN component cannot reach DERP servers in this situation:

2025-07-14 17:40:32.316 +10:00 [INF] Coder.Desktop.Vpn.Service.TunnelSupervisor - stderr: 2025-07-14 07:40:32.315 [debu]  vpn.net.wgengine: netcheck: [v1] netcheck: measuring HTTP(S) latency of coder_paris-fly (10013): dial tcp6: lookup paris.fly.dev.coder.com: getaddrinfow: The requested name is valid, but no data of the requested type was found.
...
2025-07-14 17:40:32.961 +10:00 [INF] Coder.Desktop.Vpn.Service.TunnelSupervisor - stderr: 2025-07-14 07:40:32.959 [debu]  vpn.net.wgengine: magicsock: derp.Send(127.3.3.40:10015): derphttp.Client.Send connect to region 10015 (coder_sydney-fly): dial tcp6: lookup sydney.fly.dev.coder.com: getaddrinfow: The requested name is valid, but no data of the requested type was found.

It's trying tcp6 lookups even though we don't have AAAA records on our workspace proxies, even when the tunnel supports IPv4.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions