I’ve seen this problem here already but since nothing worked there for me, I’m reopening. Also this case seems a little bit unique and I spend days to make my jitsi instance functional (failed so far).
I try to put jitsi on a little debian server (Old celeron, 3 gigs ram, debian buster x86). Issues I managed to solve so far:
Memory problem (set up 2 gigs limit for jicofo & jvb) - works!
Architecture problem with libjnisctp.so (found 32bit version, replaced in jar file)
Many of network problems from setting up right hosts entries to removing and re-installing the whole thing again! tried running on hostname domain com also on jitsi domain com, second option has best results so far
Here I’m totally stuck. Jitsi “works”, meaning no (major) errors are seen in jicofo/jvb/prosody logs, I can load up jitsi and create a room and there the pain starts. I have two laptops and so far testing on them as two participants. Jitsi is installed on the remote site. I have forwarded ports 80/443 (running apache), 4443 (to be sure), UDP 10000-20000. However any participant which connects sees all the users, but can see only his video (maybe audio). I can get no data from anyone else, so everyone has black camera and can’t be heard. Also the conference timer always begins with 1 hour which is confusing but that is not the real pain.
First real obvious error I can read from the console:
2020-04-21T09:22:36.130Z [modules/RTC/BridgeChannel.js] <_send>: Bridge Channel send: no opened channel. Logger.js:154:22 2020-04-21T09:22:36.130Z [JitsiConference.js] <se.prototype._init/this.e2eping<>: Failed to send E2E ping request or response. undefined Logger.js:154:22
tried setting in /etc/jitsi/videobridge/sip-communicator.properties
also from time to time (as troubleshooting went, maybe also at the begining this error):
ICE failed, add a STUN server and see about:webrtc for more details
This is error number
- on my list, because imho it told me the most from everything else I tried to get rid of that first - I installed coturn server. Here I got another problem because turn/stun needs to be configured twice - once in prosody and sencondly in jitsi meet. I have not found any simple uncomplicated way for all of them to talk, because in prosody I need to setup authentication with secret and in meet I need to give ready credentials which are two auth methods conflicting with each other in coturn. I don’t know how to enter username/password in prosody or secret formula into meet config which is very good so at the end I go with no auth. I’m also forwarding ports for coturn 5349 + some UDPs range for connections. Either way, even when I see some successes in coturn log / webrtc log, the data in jitsi are always same - blank…
Sorry for such a long text but I’ve invested a long long time without any success so far. Thanks for any hints.