Open DenesLieber opened 1 year ago
Please share your browser console logs.
Is your port 10000 open?
Its the same problem I'm having in https://github.com/jitsi/docker-jitsi-meet/issues/1599 I think
I fixed my issue with this by adding port forwarding between my docker host server and my VPS proxy, as well as changing some values in my .env file. My setup my be different, but I have a Wireguard tunnel from my on prem server to the cloud 10.99.99.1 and 10.99.99.2 for example.
Ubuntu Server Docker Host:
sudo iptables -t nat -A PREROUTING -p udp --dport 4443 -j DNAT --to <IP of my Proxy Host Server>:4443
sudo iptables -t nat -A PREROUTING -p udp --dport 8080 -j DNAT --to <IP of my Proxy Host Server>:8080
sudo iptables -t nat -A PREROUTING -p udp --dport 8443 -j DNAT --to <IP of my Proxy Host Server>:8443
sudo iptables -t nat -A PREROUTING -p udp --dport 10000 -j DNAT --to <IP of my Proxy Host Server>:10000
Ubuntu Server Proxy Host in the Cloud:
sudo iptables -t nat -A PREROUTING -p udp --dport 4443 -j DNAT --to <IP of my Docker Host Server>:4443
sudo iptables -t nat -A PREROUTING -p udp --dport 8080 -j DNAT --to <IP of my Docker Host Server>:8080
sudo iptables -t nat -A PREROUTING -p udp --dport 8443 -j DNAT --to <IP of my Docker Host Server>:8443
sudo iptables -t nat -A PREROUTING -p udp --dport 10000-j DNAT --to <IP of my Docker Host Server>:10000
Also check to make sure you iptables docker chain include rules to allow such traffic:
Chain DOCKER (2 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.23.0.2 tcp dpt:https
ACCEPT tcp -- anywhere 172.23.0.2 tcp dpt:81
ACCEPT tcp -- anywhere 172.23.0.2 tcp dpt:http
ACCEPT udp -- anywhere 172.23.0.2 udp dpt:10000
ACCEPT udp -- anywhere 172.23.0.2 udp dpt:8080
///output from '$docker ps' on my on perm Docker Host Server
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
<container ID> jitsi/jicofo:stable-8960-1 "/init" 2 hours ago Up 2 hours 127.0.0.1:8888->8888/tcp docker-jitsi-meet-stable-8960-1-jicofo-1
<container ID> jitsi/jvb:stable-8960-1 "/init" 2 hours ago Up 2 hours 127.0.0.1:8080->8080/tcp, 0.0.0.0:10000->10000/udp, :::10000->10000/udp docker-jitsi-meet-stable-8960-1-jvb-1
<container ID> jitsi/web:stable-8960-1 "/init" 2 hours ago Up 2 hours 0.0.0.0:8000->80/tcp, :::8000->80/tcp, 0.0.0.0:8443->443/tcp, :::8443->443/tcp docker-jitsi-meet-stable-8960-1-web-1
<container ID> jitsi/prosody:stable-8960-1 "/init" 2 hours ago Up 2 hours 5222/tcp, 5280/tcp, 5347/tcp docker-jitsi-meet-stable-8960-1-prosody-1
.env file changes:
PUBLIC_URL=10.99.99.1
JVB_ADVERTISE_IPS=<docker container jvb ip>,10.99.99.2<host IP on perm server>,10.99.99.1<host IP on cloud server>,<all public IPs from in front of and behind my Cloudflare proxy>
JVB_STUN_SERVERS=stun.l.google.com:19302,stun1.l.google.com:19302,stun2.l.google.com:19302,meet-jit-si-turnrelay.jitsi.net:443,stun.nextcloud.com:443,stun.1und1.de:3478,stun.gmx.de:3478,stun.hosteurope.de:3478
I installed jitsi server with docker compose on server with public ip without nat. When 2 people connected - all is good. When more then 2 - no audio/video, warning that a bad signal. i tried to use public ip for JVB_ADVERTISE_IPS=x.x.x.x - no result. tcpdump show ip from docker host…with stun on client side when more then 2 people connected
Please help to fix it.