No sound in Jitsi...
-
@robi apologies, not sure when I blamed anyone and I don't really understand how to apply your words to my real-life experience here... It doesn't work (stable) when running on Cloudron; it does work when installed with a script with Docker. As easy as that.
Understanding the issue is key.
Agree. And here are the facts:
It didn't work (stable) when installed on CapRover as a one-click-application. It did work like a rock when installed from the script.
Could it be a mixture of virtualization (my provider uses KVM) and Docker and Linux - maybe.
None of us seems to know that. But I see what I see - Jitsi running on Ubuntu Linux 18.04 and Ubuntu Linux 20.04 on top of KVM inside Docker is not stable.
One thing I can in common here - it's KVM, Docker & Jitsi.It doesn't seem like anyone involved has resources and or knowledge to troubleshoot this, so I see quite reasonable to repeat myself: "I'm not sure if it's something specific to Docker-izing it (as I had the same problems earlier, when it was Docker-ized under CapRover) or not."
@potemkin_ai said in No sound in Jitsi...:
apologies, not sure when I blamed anyone
It's not about blaming people or that you did so, it's about finding fault with systems that work for nearly everyone else.
You're posting here, in a Cloudron forum, where Jitsi, docker and the entire stack just works.
You had a "reading" / port issue, so this topic is solved. Right?
Perhaps it's time you look at a different VPS provider, or ask in another topic which ones have no issues with having Jitsi installed.
-
@potemkin_ai said in No sound in Jitsi...:
apologies, not sure when I blamed anyone
It's not about blaming people or that you did so, it's about finding fault with systems that work for nearly everyone else.
You're posting here, in a Cloudron forum, where Jitsi, docker and the entire stack just works.
You had a "reading" / port issue, so this topic is solved. Right?
Perhaps it's time you look at a different VPS provider, or ask in another topic which ones have no issues with having Jitsi installed.
@robi my issue is not solved; changing an ISP just to offer users to work as a guinea pig is nor easy for any complex setup, nor client-friendly.
In a way I understood, there is nothing to be done on the topic, so my best offer is to settle this as a know-issue, luckily happening not with everyone or not happening under Microsoft Hypervisor and that is has no know root cause and hence no resolution.
-
@robi my issue is not solved; changing an ISP just to offer users to work as a guinea pig is nor easy for any complex setup, nor client-friendly.
In a way I understood, there is nothing to be done on the topic, so my best offer is to settle this as a know-issue, luckily happening not with everyone or not happening under Microsoft Hypervisor and that is has no know root cause and hence no resolution.
@potemkin_ai I hear you, and the frustration behind this, however you did manage to get sound working after fixing the port issue.
Hence the topic is marked solved.
The other issues you are having are not related to Cloudron or it's supported use. That part is up to you, right?
ISPs are highly complex stacks with many moving parts.
From the networking equipment, firewall rules and other protection and network address translation technologies, each is different.
Then comes the virtualization stack and configuration, and another layer of networking specific to that inner stack.
Then you get into the OS install and Cloudron managing itself.
I hope you can appreciate that this forum helped you solve a self caused user error.
I don't agree with your conclusions, hence I am replying here to help you see where to look, however my time is limited and free consulting has its limits.
Inconvenience or not, your unmentioned choice of ISP and many nested stack isn't working for you as you expect. Hence the suggestion to try another ISP, many of which offer free trials even.
-
@potemkin_ai I hear you, and the frustration behind this, however you did manage to get sound working after fixing the port issue.
Hence the topic is marked solved.
The other issues you are having are not related to Cloudron or it's supported use. That part is up to you, right?
ISPs are highly complex stacks with many moving parts.
From the networking equipment, firewall rules and other protection and network address translation technologies, each is different.
Then comes the virtualization stack and configuration, and another layer of networking specific to that inner stack.
Then you get into the OS install and Cloudron managing itself.
I hope you can appreciate that this forum helped you solve a self caused user error.
I don't agree with your conclusions, hence I am replying here to help you see where to look, however my time is limited and free consulting has its limits.
Inconvenience or not, your unmentioned choice of ISP and many nested stack isn't working for you as you expect. Hence the suggestion to try another ISP, many of which offer free trials even.
@robi said in No sound in Jitsi...:
however you did manage to get sound working after fixing the port issue.
Hence the topic is marked solved.Not quite. I had two issues:
-1. Related to the port. Fixed. Indeed.
-2. Blinking issue with Jitsi not-working from time to time.Everything I say here is about second problem.
And yes, I'm aware how ISP works. I used to work for at telecom and other interesting places with a very extensive tech. stack.Hope that makes sense.
-
@opensourced the repo for the Cloudron package is at https://git.cloudron.io/cloudron/jitsi-app
Thanks for the offer, but it is not quite clear how a VM will help us to reproduce this. At least I wasn't able to reproduce this on a few Cloudrons I've tried and eventually gave up.
@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?
-
@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.
