Skip to content

v10.0.7-alpha — One TURN port per job: Remote Assist always on 3479, NetBird always on 3478

Choose a tag to compare

View all tags
@takwerx takwerx released this 03 Jul 05:08
v10.0.7-alpha
1b2130f

A small, focused release that removes an install-order trap between the EUD Remote Assist TURN server and NetBird.

The permanent port split

  • CoTURN (Remote Assist) now always installs on port 3479 — on every server, whether or not NetBird is present. Remote Assist clients are told the address and port explicitly by the module, so nothing depends on the standard TURN port.
  • Port 3478 is permanently reserved for NetBird, which requires it.

Previously the suggested CoTURN port depended on what was already installed: 3478 on a clean box, 3479 next to NetBird. That made the "right" port vary from box to box — and a box that installed CoTURN first on 3478 would break a later NetBird deployment with a raw Docker port is already allocated error.

NetBird deploy pre-flight

If an older CoTURN install is still holding 3478, deploying NetBird now refuses up front with clear instructions — uninstall CoTURN and reinstall it (the installer lands on 3479 automatically, reuse the same credentials) — instead of failing halfway through.

Notes

  • Existing CoTURN installs keep working unchanged on whatever port they were installed with. No forced migration.
  • New installs: open UDP/TCP 3479 and UDP 50000–50050 in your cloud security group / upstream firewall (the on-box firewall is configured automatically).
  • Validated on Ubuntu 22.04, Rocky/RHEL 9, and ARM64 — including a fresh ARM64 Remote Assist + CoTURN install that landed on 3479 first try.

Upgrade

Applied automatically on the next console update (Update Now or git pull + restart). No action required unless you plan to add NetBird to a box whose CoTURN sits on 3478 — the deploy will tell you exactly what to do.

Assets 2
Loading