[jitsi-users] Nginx not installed by quick install on Ubuntu 17.04


#1

Greetings.

This is an awesome project; I'm excited to get a video bridge going.

I installed a pristine version of Ubuntu 17.04 Server on a computer, and
then proceeded to follow the Jitsi Meet Quick Install instructions at
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md .

When it got to the step to open up a conference, it didn't work. After
poking around, I was able to see that prosody was set up (very slick!), and
seems to be working, but nginx was not even installed, much less
configured. I believe I followed the instructions carefully and that they
should work.

I have since been following the manual installation instructions for nginx,
and finally got letsencrypt to give me a certificate [1], but when I try to
connect, I get: curl: (35) Unknown SSL protocol error in connection to
192.168.0.100:-9847

Two questions:
- do self-signed certs work reasonably well?
- while I would prefer an encrypted connection, does Jitsi Meet work over
HTTP?

Cheers,
Clinton Blackmore

[1] following
https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04


#2

Greetings.

This is an awesome project; I'm excited to get a video bridge going.

I installed a pristine version of Ubuntu 17.04 Server on a computer, and
then proceeded to follow the Jitsi Meet Quick Install instructions at
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md .

When it got to the step to open up a conference, it didn't work. After
poking around, I was able to see that prosody was set up (very slick!), and
seems to be working, but nginx was not even installed, much less
configured. I believe I followed the instructions carefully and that they
should work.

Nginx has to be installed prior to installing Jitsi Meet, then it will be
set up accordingly.

I have since been following the manual installation instructions for nginx,
and finally got letsencrypt to give me a certificate [1], but when I try to
connect, I get: curl: (35) Unknown SSL protocol error in connection to
192.168.0.100:-9847

Two questions:
- do self-signed certs work reasonably well?

Yeah. Jitsi meet works with self signed certs in nginx and/or prosody. But
will your users trust your application?

- while I would prefer an encrypted connection, does Jitsi Meet work over
HTTP?

WebRTC features such as getUserMedia requests won't work in Chrome with
HTTP although it may work in other browsers.

Cheers,
Clinton Blackmore

[1] following https://www.digitalocean.com/community/tutorials/
how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04

···

On Apr 15, 2017 8:52 PM, "Clinton Blackmore" <clinton.blackmore@gmail.com> wrote:

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Good to know.

Incidentally, following the quick instructions on Ubuntu 16.04.2 LTS worked
just fine, including installing nginx and creating the self-signed certs.

Cheers,
Clinton Blackmore

···

On Mon, Apr 17, 2017 at 5:34 AM Camilo <camilo@camilo.fm> wrote:

On Apr 15, 2017 8:52 PM, "Clinton Blackmore" <clinton.blackmore@gmail.com> > wrote:

Greetings.

This is an awesome project; I'm excited to get a video bridge going.

I installed a pristine version of Ubuntu 17.04 Server on a computer, and
then proceeded to follow the Jitsi Meet Quick Install instructions at
https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md .

When it got to the step to open up a conference, it didn't work. After
poking around, I was able to see that prosody was set up (very slick!), and
seems to be working, but nginx was not even installed, much less
configured. I believe I followed the instructions carefully and that they
should work.

Nginx has to be installed prior to installing Jitsi Meet, then it will be
set up accordingly.

I have since been following the manual installation instructions for
nginx, and finally got letsencrypt to give me a certificate [1], but when I
try to connect, I get: curl: (35) Unknown SSL protocol error in
connection to 192.168.0.100:-9847

Two questions:
- do self-signed certs work reasonably well?

Yeah. Jitsi meet works with self signed certs in nginx and/or prosody. But
will your users trust your application?

- while I would prefer an encrypted connection, does Jitsi Meet work over
HTTP?

WebRTC features such as getUserMedia requests won't work in Chrome with
HTTP although it may work in other browsers.

Cheers,
Clinton Blackmore

[1] following
https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users