Repository navigation
fix: announce LiveKit's external IP behind NAT - #866
Merged
antobinary merged 1 commit intoOct 28, 2026
Merged
Conversation
Behind NAT, bbb-install sets the external IP for FreeSWITCH and mediasoup, but not for LiveKit. LiveKit then learns its external address from public STUN servers (Google, Twilio) on every connection, and announces no public address when outbound STUN is blocked. Set rtc.node_ip to the external IP, as the 4.0 firewall docs ask, so no STUN lookup is needed. LiveKit keeps that IP until bbb-install runs again behind NAT. Also set rtc.advertise_internal_ip: node_ip alone would stop LiveKit announcing the private address, which users on the private network and on-host components use today. This needs livekit-server 1.13.6. 1.13.0-1.13.5 ignore advertise_internal_ip when node_ip is set, and 1.9 (BigBlueButton 4.0.0) refuses to start with it. On older versions bbb-install sets neither key; re-running it after the LiveKit upgrade sets them.
prlanzarin
force-pushed
the
binst40/chore/lk-nip-adv
branch
from
October 28, 2026 21:11
afff43f to
d8a3340
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Behind NAT, bbb-install now sets
rtc.node_ipto the external IP in/etc/bigbluebutton/livekit.yaml, as it already does for FreeSWITCH and mediasoup. LiveKit then announces the external address without asking public STUN servers (Google, Twilio) on every connection.It also sets
rtc.advertise_internal_ip: true. Withnode_ipalone, LiveKit stops announcing the private address, which users on the private network and on-host components use today.The step needs livekit-server 1.13.6 or later, which the
v4.0.x-developpackages ship (1.13.7). livekit-server 1.9 (BigBlueButton 4.0.0) refuses to start withadvertise_internal_ip, and 1.13.0-1.13.5 ignore it whennode_ipis set. On older versions bbb-install sets neither key, and re-running it after the LiveKit upgrade sets them.How to test
On a host behind 1:1 NAT (a public IP mapped to a private address on the NIC, as on EC2):
/etc/bigbluebutton/livekit.yamlhasrtc.node_ip: <external IP>andrtc.advertise_internal_ip: true, andjournalctl -u livekit-servershowsusing explicit node IP for NAT1To1Ipswith"advertiseInternalIP": true.livekit-server 1.9.12: not configuring LiveKit for NAT (advertise_internal_ip needs 1.13.6 or later),livekit.yamlgets no new keys, and livekit-server starts.livekit.yamldoes not change.Changelog
Technical — Behind NAT, bbb-install sets LiveKit's
rtc.node_ipandrtc.advertise_internal_ipwith livekit-server 1.13.6 or later.User-facing — None.