This message was deleted.

Getting this too if I provide a config.yaml. Not in dev mode. Looks like STUN is required to determine the public ip. However the server is working in local network regardless of this

cc @echoing-kitchen-90064

Hey ya'll, as Neil mentioned, livekit server requires STUN servers to determine it's public ip. There are defaults set here https://github.com/livekit/mediatransportutil/blob/master/pkg/rtcconfig/config.go#L35-L38 but you can override these by setting the STUNServers in the config https://github.com/livekit/mediatransportutil/blob/master/pkg/rtcconfig/config.go#L47 You can run livekit server without a public ip if local access is all that is needed; if that's the case you can safely ignore this error.

I do require an external IP address, but I would like to disable the validation

I‘m not entirely sure, why livekit server mandates STUN at all, but it is a design decision IMHO. Could be done one way or the other. Mediasoup has a config for the public IP of the server and doesn’t use or require STUN/TURN at all. But at least a „reachable“ public IP should be given, otherwise no media will ever arrive at your server.

Thank you @adventurous-twilight-28575 I have a publicly accessible IP, I just don’t want my LiveKit server to expose my configured IP to non-authorized clients. Sending a request to a public STUN like Google’s basically exposes my IP to google. Does that make sense to you?

You will have to expose it anyway, otherwise the far end will not know where to send the media to.

Expose it only to my validated and authorized clients only

Ah I see. Sorry, didn’t get this until now. Well, my least concern up to now was to expose my server’s public IP via STUN, but I agree, this concern is valid. Ok, for this you only have the choice to find a way to configure it manually to live kit server, I would guess, but my experience with LK is one day old.

Oh haha 😅 by reading LiveKit’s code, I think it is currently not supported. As long as the local available ip addresses are not used (bound) as the main ip for livekit, then it will try to reach an external STUN to find the actual IP address.

PR possibly? There is plenty of space in config.yaml to achieve this I would guess 😀