Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat(coderd/healthcheck): improve detection of STUN issues #12951

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

Merged
merged 13 commits into from
Apr 15, 2024
Prev Previous commit
Next Next commit
document STUN warnings
  • Loading branch information
johnstcn committed Apr 12, 2024
commit 56f81fc6b5b5c3774f72b8953c22a01836a4dbfe
25 changes: 25 additions & 0 deletions docs/admin/healthcheck.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,31 @@ curl -v "https://coder.company.com/derp"
# DERP requires connection upgrade
```

### ESTUN01

_No STUN nodes available._

**Problem:** This is shown if no STUN-capable nodes are available. Coder will
use STUN to establish [direct connections](../networking/stun.md). Without at
least one working STUN server, direct connections may not be possible.

**Solution:** Ensure that the
[configured STUN severs](../cli/server.md#derp-server-stun-addresses) are
reachable from Coder and that UDP traffic can be sent/received on the configured
port.

### ESTUN02

_Mapping varies based on destination IP. You may be behind a hard NAT._

**Problem:** This is a warning shown when multiple attempts to determine our
public IP address/port via STUN resulted in different `ip:port` combinations.
This is a sign that you are behind a "hard NAT", and may result in difficulty
establishing direct connections. However, it does not mean that direct
connections are impossible.

**Solution:** Engage with your network administrator.

## Websocket

Coder makes heavy use of [WebSockets](https://datatracker.ietf.org/doc/rfc6455/)
Expand Down
Loading