16 ms·

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-in

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 6y 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 6y 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 6y 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 6y 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 6y 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 6y ago
        https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
    - villgax 6y 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 6y ago
https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649

EvanAnderson 6y 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 6y 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 6y 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 6y 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 6y 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 6y ago
      https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649
  - villgax 6y 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 6y ago

https://github.com/jitsi/jitsi-meet/issues/5649 https://github.com/jitsi/jitsi-meet/issues/5649