Thanks — you're asking whether to set

use_external_ip

or

node_ip

. To give the right recommendation I need a bit more context: • Are you running LiveKit behind NAT (cloud VM with private and public IP) or on a host with a single public IP? • Is LiveKit behind a load balancer or reverse proxy (e.g., Kubernetes Service, cloud LB)? • Do you want clients to connect directly to the node's public IP, or will a proxy/LB handle public access? • Are you configuring this for TURN/STUN or for the LiveKit server config? Quick guidance while you reply: • If the node has both a private and a reachable public IP and you need the server to advertise the public address to clients,

use_external_ip

is typically used to advertise the external/public IP. • If you want to force the server to bind/advertise a specific IP address (for example the node's private interface), set

node_ip

to that interface IP. Tell me your environment (NAT vs public, LB vs direct, and whether this is for TURN/STUN or server binding) and I’ll recommend the exact setting and example config.