No sound in Jitsi...
-
I keep trying to experiment with Jitsi package in CloudRon and I have encountered a new problem - there is no sound going through the conference.
Microphone is there, all of the access in the browser is granted, but we can't hear each other.
At the meantime rolled back to the self-hosted Jitsi without the Docker, but I would love to have Jitsi running on Cloudron - any help would be much appreciated.
-
@potemkin_ai so video works, but sound does not? Do you see any related errors in the client or app itself? Also is this with 2 participants or more? This may be relevant, as jitsi transmits video and sound differently if 2 or 3+ participants are in a conference.
With 2 it uses direct connection between the clients, from 3 participants on, all clients send data to the server which relays then. -
@nebulon thanks for the prompt responce!
Nor video nor sounds works, for 2 or 3 participants.Strange enough, it shows that all other conference members are muted - in both 3 participants and 2 participants mode, however they are not muted.
-
@potemkin_ai for a start the 3 participant meeting should go via the app instance on port
10000
this is hardcoded in jitsi and can't be changed, so make sure this port is reachable from your client.Further you likely see some connection errors in the browser logs as well as the connection candidates it found for webrtc, so check those.
On top of this, are you using Cloudrflare proxying by any chance for this domain? Just thought of this and it likely will break due to the extra port not forwarded by CF then.
-
N nebulon marked this topic as a question on
-
Also, are you all on good internet connections?
Jitsi will automatically turn off cameras etc to try to ensure the meeting can go on when people have bad connections.
-
@jdaviescoates thank you, didn't know that, but it's out of question, the internet is stable
-
@potemkin_ai the only reason we show it is, that our dashboard has no exception for such a case, which is why the description says "only default works" hopefully upstream supports other ports at some point though.
Is this solved then with the default port?
-
N nebulon has marked this topic as solved on
-
@nebulon , unfortunately, it doesn't work again...
The video and audio doesn't work even for 2 participants for me and users report that it stops transmitting the sound after 3rd user attached.Can't upload full log file due to forum restriction, but here is what seems to be a key lines:
BridgeChannel.js:84 WebSocket connection to 'wss://server.domain/colibri-ws/default-id/9e492323b5fe10c7/2dd3002a?pwd=2dhurejj37lfravd497k7t2jo7' failed: _initWebSocket @ BridgeChannel.js:84 t @ BridgeChannel.js:103 Logger.js:154 2022-08-15T07:24:24.118Z [modules/RTC/BridgeChannel.js] <e.onclose>: Channel closed by server Logger.js:154 2022-08-15T07:24:24.118Z [modules/RTC/BridgeChannel.js] <e.onclose>: Channel closed: 1006 r @ Logger.js:154 e.onclose @ BridgeChannel.js:433
The port is 10'000, nothing has been changed there.
Any help would be much appreciated!
-
Check Cloudron services to make sure your TURN server is working.
Otherwise, I would uninstall and reinstall to make sure the port is unchanged everywhere.
Is any other upstream firewalling or routing happening or do you have a public IP for it?
It's been pretty bulletproof here otherwise.
-
@potemkin_ai and your fw has open ports for the Cloudron TURN server?
-
I think you have to report this upstream as we are no jitsi experts here and given that the other instances of the package on Cloudron work fine, this may be some specific error with your routing setup. Generally only on the 3rd partivipant the video (and audio) bridge will be used but that is pretty much just a simple relay.
-
@potemkin_ai have you made progess so far?
I have been running into the similar (if not even the same) issue here. My VM is behind a firewall in a LAN. Ports are open and everything is ready to go, but sound and image doesn't work.
The interesting thing is, that running Jitsi on Yunohost, works like a charm. Compared to your situation with your other working instance of Jitsi, i would assume a configuration issue. I have started analyzing the config files, however not found a solution so far.
If i find a solution, i will post it here...
Cheers