https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
i
I don't have ufw enabled. Here are the results of netstat -tulpen:
Copy code
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 127.0.0.1:6011          0.0.0.0:*               LISTEN      1000       107898     -
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN      1000       101619     -
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      102        53490      -
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          52697      -
tcp6       0      0 :::7880                 :::*                    LISTEN      1000       39217      12738/livekit-serve
tcp6       0      0 :::7881                 :::*                    LISTEN      1000       96963      12738/livekit-serve
tcp6       0      0 ::1:6011                :::*                    LISTEN      1000       107897     -
tcp6       0      0 ::1:6010                :::*                    LISTEN      1000       101618     -
tcp6       0      0 :::22                   :::*                    LISTEN      0          52699      -
udp        0      0 127.0.0.53:53           0.0.0.0:*                           102        53489      -
udp        0      0 192.168.1.70:68         0.0.0.0:*                           101        99559      -
udp6       0      0 fe80::5a11:22ff:fec:546 :::*                                101        57487      -
Tried opening udp ports via the following but made no difference
Copy code
sudo iptables -A INPUT -p udp --dport 50000:60000 -j ACCEPT
Even went explicit with the tcp ports (since I am only using ipv4) but to no avail:
Copy code
sudo iptables -A INPUT -p tcp --dport 7880 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 7881 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 7882 -j ACCEPT
I'm sure I'm missing something very basic but at this point I'd appreciate some guidance.
d
did you include the port when performing connection test? by default livekit-server runs on 
:7880
from Meet, it's not able to connect to an unsecure websocket (that's not localhost) so you'd want to do:
Copy code
<ws://localhost:7880>
i
I have tried with and without the port being explicitly defined but it didn't make a difference in the connection test.
when I try Meet from my laptop browser to ws://192.168.1.70:7880 or ws://192.168.1.70 the page simply spins with the title "Connecting". When I try with wss://192.168.1.70:7880 the page immediately responds with the title "Disconnected". If I try Meet without the port (wss://192.168.1.70) then the page first starts with "Connecting" and then transitions to "Disconnected". BTW, if I reload the Meet page I see a message flash which says "Missing LiveKit URL" (regardless whether the ws: or wss: URL entered had the port or not).
None of these attempted connections from my laptop (connection-test or meet) resulted in a message on my shell running "livekit-server --dev --bind 0.0.0.0". I would expect some sort of debug output...
I've just attempted "*sudo* livekit-server --dev --bind 0.0.0.0" and obtained the same results across the board.
If I try to access port 7880 from my laptop via http:
Copy code
<http://192.168.1.70:7880>
I receive "OK"
d
as mentioned.. you need to connect to 
localhost
if using Meet.. browser security policies disallow you to connect from a secure URL (https://meet.livekit.io) to an insecure URL (ws://yourhost:7880).. the only exception to that rule is 
localhost
, you are always allowed to connect to your own computer
i
Thanks @dry-elephant-14928. This is a headless server and I don't have a browser or even UI installed so localhost used in this manner will be a challenge. Am I correct in my understanding that I will have the same problem using https://livekit.io/connection-test since it is a secure site and (based on your responses) the likekit-server -dev is only listening to the insecure ws:// ? If so I think I will just jump toward the deployment path for the server and set up the secure channels to work with connection-test and with Meet.
Scratch that. Was able to run the livekit-server --dev against the localhost run livekit-cli bot-user as a fake participant (https://docs.livekit.io/getting-started/cli-setup/). Things seems to be working
d
glad you figured out a workaround.. If this server is to be exposed to the public, take a look at setting up a VM, which includes SSL termination.
43 Views
Open in Slack
PreviousNext
Powered by