This message was deleted.

For what is worth, running the generated docker-compose in a remote server works like a charm 😄. Great job on making that super easy!

Welcome @lively-oyster-78885! The

--dev

flag doesn't work quite as well with Docker. For security, we automatically bind to 127.0.0.1 by default (since it uses placeholder keys). To get around this, you can override the bind address with

--bind 0.0.0.0

, which will allow it to take requests from any source IP.

Hi David! Thanks a lot for your help and time, I really appreciate it 😄 Wasn't aware of the

--bind

flag, and that absolutely did it! I got the local container running 🎉 Now, I'm facing another issue where I get this in the Firefox console when running the LiveKit example:

WebRTC: ICE failed, add a TURN server and see about:webrtc for more details

But I'm sure that is solvable by tweaking the config a bit when running the server (my first guess would be exposing the

ICE/UDP

of the container as well). For reference, I'm running this:

docker run --rm -p 7880-7882:7880-7882 -p 5349:5349 --rm livekit/livekit-server --dev --bind 0.0.0.0

I'll play around a bit and update in this thread if I get it to work. Thanks again!

yay! glad to hear

--bind

worked. Looking at your docker command, it doesn't appear that it's forwarding UDP. it'd need to be forwarded explicitly like

-p 7882:7882/udp

Oh, interesting. I was under the impression that when it wasn't explicit, docker would open for both protocols, good to know. So I tried, but still getting the same message in Firefox console. What's interesting is that I can see the connection activity in the server, so the connection is established. Taking a closer look at the logs, the connection starts fine until this happens:

livekit	service/rtcservice.go:283	exit ws read loop for closed connection	{"room": "my-first-room", "roomID": "RM_J9oYgR8CPVSf", "participant": "user1", "remote": false, "connID": "CO_kURZYuTsmmw5"}

After that the connection is marked as failed and the tear down process begins to close the connection. Also, I'm able to see in Firefox the messages sent through web sockets, until the connection is closed. All in all, progress 😄, but still unable to connect to it. By the way, I'm using the LiveKit react example to test. Again, thanks a lot for your time. I'll play around and see if I can spot the issue and write here if I have any updates

ah I think you'd need to set --node-ip as well, it should be set to the IP where clients would be able to reach

For a server running locally, it should be something like

--node-ip 127.0.0.1

?

that should work for your local machine