This message was deleted.
# helpdesk
s
This message was deleted.
a
cc @early-gigabyte-44411 who might be able to help. or @great-umbrella-58130 when he’s online
e
If your vm can’t access public internet ,you should disable the
use_external_ip
in the config
g
public IP look up happens with external STUN servers: https://github.com/livekit/livekit/blob/master/pkg/config/ip.go
If you’re sure your server can reach the internet, you can also specify
node-ip
via config
e
The log shows the VM have a public internet access and resolved
178.128.164.109
, it looks no problem if it is your public ip. The other
failed to get external ip
log will not affect your connection, they are just a information that your private ip
10.x.x.x
only can be access by intranet. Can you post the client’s candidate info in the
webrtc-internals
of your browser, and log from livekit-server
p
here's more logs from livekit-server and a screenshot from webrtc-internals. thank you so much for your valuable feedback!
e
Your
webrtc-internals
tab is empty, you need keep this tab open, then do the connection test again, it will record your webrtc events.