LiveKit Community

image.png

did you set `use_external_ip` to true? does `nodeIP` indicate a public or private address?

<@U01KZ61GV5Z> I had to add explicitly add `node_ip` to the helm-rendered configmap since there’s no support for this on the charts :thinking_face:

I managed to get responses from the server when I do `wget &lt;VM external IP&gt;:7880/twirp/livekit.RoomService/&lt;method name&gt;`

But still `ws://` doesn’t work and test fails

Now I managed to run `livekit-cli load-test` successfully, lot’s of logs appear on the server’s pod, and also on the service I wrote that gets the webhooks from the LK server..

But still, and that’s the weird part- the LK tester isn’t connecting (stuck on a loop)

is it a insecure (`ws://`) url? if so you would not be able to connect to it from the connection tester. this is the browser's security policy

Indeed it is an insecure URL.
There’s no way whatsoever to to have a webRTC session on browsers with no certificates for the domain?

you have to host the page on http instead of https.. you can do http -&gt; ws, but not https page -&gt; ws