No sound in Jitsi...
-
@nebulon I actually have set up several Cloudron instances and none of them is able to get Jitsi to work. I suppose that if I provide a fresh VM, it wont be able to get it working either. Therefore it might be suitable for debugging.
(I still want to mention at this point that its neither port related, nor a networking issue as I have a working Jitsi (from Yunohost) on one of my VMs)
What do you think?
-
@opensourced Can you tell us on which VPS provider you tried to setup Jitsi? We can then test them out there. Our cloudron/jitsi instances are hosted in DO and they work fine there atleast.
-
@girish We do have our own server farm in a data center. As host for our VMs, we use Proxmox.
@opensourced Think we found a few variables that we can set in Jitsi (that the package currently does not set). We will release a new package shortly with the changes.
-
@opensourced Think we found a few variables that we can set in Jitsi (that the package currently does not set). We will release a new package shortly with the changes.
@girish thanks, I'm still looking for ways to move Jitsi running on Cloudron, and would love to unroll my manual installation server.
-
The latest package now has a TCP harvester port defaulting to 4443. At least in my tests changing that or the UDP harvester port 10000 will result in no connectivity. Not sure how to fix this, but hopefully adding TCP improves the situation.
The NAT settings were unclear to me as what to set when using a docker bridge, so those are not part of this package release but hopefully we get down to what they should be set to for the next release then.
-
The latest package now has a TCP harvester port defaulting to 4443. At least in my tests changing that or the UDP harvester port 10000 will result in no connectivity. Not sure how to fix this, but hopefully adding TCP improves the situation.
The NAT settings were unclear to me as what to set when using a docker bridge, so those are not part of this package release but hopefully we get down to what they should be set to for the next release then.
@nebulon thank you!
I've run out of the patience limit for my clients, so I've got to wait for the next package release. Keep fingers crossed! -
The latest package now has a TCP harvester port defaulting to 4443. At least in my tests changing that or the UDP harvester port 10000 will result in no connectivity. Not sure how to fix this, but hopefully adding TCP improves the situation.
The NAT settings were unclear to me as what to set when using a docker bridge, so those are not part of this package release but hopefully we get down to what they should be set to for the next release then.
@nebulon said in No sound in Jitsi...:
The NAT settings were unclear to me as what to set when using a docker bridge, so those are not part of this package release but hopefully we get down to what they should be set to for the next release then.
At the bottom of the variables page @girish found, there's a link to a previous page -> docker guide that has NAT info and reverse proxy setup considerations.
-
@opensourced Think we found a few variables that we can set in Jitsi (that the package currently does not set). We will release a new package shortly with the changes.
@girish I'm glad to see your efforts put in this issue. I think we are getting closer! I looked at the sip-communicator config of yunohost - as their jitsi is working on my systems and they actually set those variables.
A further indication that this is the only missing piece is this thread here...
Are there environment variables for the local and the public IPs? I would like to test this.
-
@girish , I understand this topic is marked as solved and might fall out of sight - so I'm wondering if there are any updates on that?
-
P potemkin_ai referenced this topic on
-
P potemkin_ai referenced this topic on
-
@girish , I understand there are no updates?
-
@potemkin_ai No updates. We can't reproduce this and I am not sure what we can do to debug this further.
@girish right... but if felt like you found something to check (https://forum.cloudron.io/post/55044) - from what I understand, it won't hurt at least?
-
@opensourced Think we found a few variables that we can set in Jitsi (that the package currently does not set). We will release a new package shortly with the changes.
@girish is there any way I can add those variables persistently just on my instance, to verify if they solve the issue and to make sure it doesn't brake anything?
If that would work, I would revert back to you and you will only need to merge them into the source tree and everyone would be happy.
How does it sound?
I really hate having separate machine just for Jitsi.
-
Raising this up, in case it got lost.
-
@potemkin_ai We are still reworking the package (the package has fallen a bit behind since we couldn't figure how to update with ubuntu 22). Will pick this up next week.
@girish thank you! Keep fingers crossed, I really need Jitsi working on Cloudron
-
btw, the script I'm using requires Ubuntu 20.04 LTS, guess there might be a reason for that...
