AZIS: network requirements

Devices join AZIS with the NetBird client. Before anyone at your site enrolls, your network must allow the outbound connections below. Many organisation networks allow the first row (ordinary HTTPS) but block the others.

What to allow

Host namePort / protocolPurposeNeeded
netbird.azis.lvTCP 443Joining the network (control)Usually already allowed
stun.cloudflare.comUDP 3478Path discovery (STUN)Strongly recommended
Other AZIS devices (any address)UDP, high portsDirect connections between devices; faster than relayingRecommended

Allow every host listed: a device opens connections to more than one relay.

Check before you start

Run this from a computer on your site network. It must report the connection as succeeded or open.

nc -zv <relay host> <relay port>

If it is blocked

NetBird shows "Connected" but 0 peers connected, and the login link does not open. The device has registered, but it cannot reach any other device, so no AZIS service is reachable from it. Run netbird status -d: if relays show context deadline exceeded and the peer count is 0, the site network is blocking the ports above.