5 ms·

Jitsi despite its frequent re-occurence here is a nightmare to configure with so many bells & whistle to setup just one basic functionality. Try setting it up w

Jitsi despite its frequent re-occurence here is a nightmare to configure with so many bells & whistle to setup just one basic functionality. Try setting it up with word-to-word instructions for setup & later SSL certs to work on your own iOS app of Jitsi meet without ripping your hair out.

oxidising 7y ago
This hasn't been my experience at all. Setting it up on a VM using their installation instructions (https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-in...) was very easy.
- EvanAnderson 7y ago
  Same experience here. I had a VM up and running in about 30 minutes. (Having said that, I never got test meetings to work reliably. My clients, both on the LAN and on the Internet, would repeatedly "disconnect" and "reconnect" every few seconds. I didn't spend too much time on it because the company ended up making a "let's standardize on WebEx" decision the next day.)
- xrd 7y ago
  Super easy for me. I followed the instructions to setup on Ubuntu and it was ten minutes with zero confusion. Just copy the steps from the guide. Even the let's encrypt script installed certbot and configured whatever was needed with the existing web server. Then I just hit the url and it worked perfectly. The biggest surprise was when I tried to access that same page from an Android phone. It prompted me to install the jitsi app. After I installed it, it directed me to my jitsi server. For me it was flawless and even better that I expected. It's a strong competitor to zoom because of the fact that it works right inside the browser really well.
  - villgax 7y ago
    Android isn't the problem, I mentioned iOS. I know WebRTC works and all starting iOS 11, but the problem remains with the way Jitsi configures SSL in the nginx conf. iOS Safari is simply unable to establish a secure connection despite the server having a valid LetEncrypt cert.
    - saghul 7y ago
      Hey there, saghul from Jitsi here. Have you reported that to us? I have deployed several self-hosste instances with Lets Enccrypt and haven't seen this, but there might a bug lurking somewhere.
      - leesalminen 7y ago
        There was a version of nginx that broke TLS for Safari when HTTP/2 is enabled. This was a number of years ago now and I’m sure isn’t happening on new versions.
        villgax 7y ago
        https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
      - villgax 7y ago
        Hi dude, great job on Jitsi though, this is the latest one https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
- villgax 7y ago
  https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
fleetside72 7y ago
It not my experience at all. In fact it was the easiest install I have ever done. It knew I was using nginx as a reverse proxy and inserted itself correctly as a subdomain. The only issue I had was webmin was running on port 10000 which created a conflict because it also wanted to bind to 10000.
- polote 7y ago
  After reading your message, I tried installing it on archlinux, and here we are 3 hours later and I still didnt figure out to make it work, so I'm sadly giving up
  - fleetside72 7y ago
    what kind of issues you running into? hit me up. paul@hptrow.me
eeZah7Ux 7y ago
I'd rather use Janus
- xenonite 7y ago
  could you elaborate a bit?
SparkyMcUnicorn 7y ago
This is the case if you're doing a completely custom configuration. Their quick install took me about 5 or 10 minutes to set up. https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-in...
- villgax 7y ago
  The issue was with the way TURN & nginx were dealing with SSL https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
villgax 7y ago
This is the SSL issue with NGINX JITSI CONF & TURN in the tow https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649

oxidising 7y ago

This hasn't been my experience at all. Setting it up on a VM using their installation instructions (https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-in...) was very easy.

EvanAnderson 7y ago
Same experience here. I had a VM up and running in about 30 minutes. (Having said that, I never got test meetings to work reliably. My clients, both on the LAN and on the Internet, would repeatedly "disconnect" and "reconnect" every few seconds. I didn't spend too much time on it because the company ended up making a "let's standardize on WebEx" decision the next day.)
xrd 7y ago
Super easy for me. I followed the instructions to setup on Ubuntu and it was ten minutes with zero confusion. Just copy the steps from the guide. Even the let's encrypt script installed certbot and configured whatever was needed with the existing web server. Then I just hit the url and it worked perfectly. The biggest surprise was when I tried to access that same page from an Android phone. It prompted me to install the jitsi app. After I installed it, it directed me to my jitsi server. For me it was flawless and even better that I expected. It's a strong competitor to zoom because of the fact that it works right inside the browser really well.
- villgax 7y ago
  Android isn't the problem, I mentioned iOS. I know WebRTC works and all starting iOS 11, but the problem remains with the way Jitsi configures SSL in the nginx conf. iOS Safari is simply unable to establish a secure connection despite the server having a valid LetEncrypt cert.
  - saghul 7y ago
    Hey there, saghul from Jitsi here. Have you reported that to us? I have deployed several self-hosste instances with Lets Enccrypt and haven't seen this, but there might a bug lurking somewhere.
    - leesalminen 7y ago
      There was a version of nginx that broke TLS for Safari when HTTP/2 is enabled. This was a number of years ago now and I’m sure isn’t happening on new versions.
      - villgax 7y ago
        https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
    - villgax 7y ago
      Hi dude, great job on Jitsi though, this is the latest one https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
villgax 7y ago
https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649

fleetside72 7y ago

It not my experience at all. In fact it was the easiest install I have ever done. It knew I was using nginx as a reverse proxy and inserted itself correctly as a subdomain. The only issue I had was webmin was running on port 10000 which created a conflict because it also wanted to bind to 10000.

polote 7y ago
After reading your message, I tried installing it on archlinux, and here we are 3 hours later and I still didnt figure out to make it work, so I'm sadly giving up
- fleetside72 7y ago
  what kind of issues you running into? hit me up. paul@hptrow.me

eeZah7Ux 7y ago

I'd rather use Janus

xenonite 7y ago
could you elaborate a bit?

SparkyMcUnicorn 7y ago

This is the case if you're doing a completely custom configuration. Their quick install took me about 5 or 10 minutes to set up. https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-in...

villgax 7y ago
The issue was with the way TURN & nginx were dealing with SSL https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649

villgax 7y ago

This is the SSL issue with NGINX JITSI CONF & TURN in the tow https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649