Some people I use meet with cannot use outgoing udp on port 10000 in their network, so I changed it to port 86 (with
org.jitsi.videobridge.SINGLE_PORT_HARVESTER_PORT=86 in the videobridge properties)
This is working fine for browser clients, but not in the app (tested on android. I can connect to a meeting but I am not getting/sending video and audio).
The app was working fine with my server (using the standard port 10000) before this change though and still is if I change it back.
I then assumed the app is just always using port 10000 and tried redirecting traffic from port 10000 to port 86 on my machine with:
iptables -t nat -A PREROUTING -p udp --dport 10000 -j REDIRECT --to-port 86
but this is not working either. What could be the issue here?
Is there a way to tell the app to use my custom port? Or am I redirecting traffic from port 10000 to 86 wrong?
Info about my installation:
- This is the guide I followed: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart
- Since there already is a machine in my network hosting a webserver on ports 80/433 I chose port 85 for jitsi. I installed jitsi by following the guide, then changing the ssl listen port to 85 in the nginx config and the
BOSH URLto include
:85after my FQDN in jitsi’s config.js. My meet instance is now available at
https://meet.mydomain.com:85/and with this url it is working fine in the browser and also in the app (as long as the videobridge is running on port 10000)
- My router is forwaring ports
tcp/85(for the https web interface) and
udp/86(for the videobridge) to the machine running the jitsi server (and also
udp/10000). I did not open a port for http.
- I have a let’s encrypt certificate for the server and https://whatsmychaincert.com/ reports the chain to be correct
- I did not open the ports for the TURN/STUN servers and neither did I enable them in the config. P2P is turned off.
- I am running the jitsi server on Ubuntu 20.04.1 LTS