Jitsi Installation Guide Ubuntu14 Apache2
Jitsi Installation Guide Ubuntu14 Apache2
Jitsi Installation Guide Ubuntu14 Apache2
Ubuntu14.04 + Apache2
This guide provides instructions how to install Jitsi WebRTC server on Ubuntu14.04 with existing Apache2 web
server.
It is assumed that we already have working domain on https://qqq.com and we need make working Jitsi video
conference and existing web content.
Must use Сhrome or Firefox browser.
The commands in this guide require root privileges.
rm -rf /etc/jitsi
Prosody
rm -rf /etc/prosody
dpkg -i init-system-helpers_1.18_all.deb
3. Install jitsi-meet
Follow jitsi-meet installation guide for Ubuntu on https://jitsi.org/downloads/.
All installation steps should pass without errors.
Pay attention for SSL certificates settings.
tail -f /var/log/prosody/prosody.log
After jitsi default installation you will see messages like below in prosody.log:
Feb 06 12:51:24 mod_bosh info New BOSH session, assigned it sid '95608d52-2798-4c00-97fa-001763675527'
Feb 06 12:51:24 bosh95608d52-2798-4c00-97fa-001763675527 info Authenticated as dd9a7992-ebd8-4c46-896f-4aeb6096d28b@qqq.com
Lots of:
Feb 06 12:51:26 c2s159cf90 info Client connected
Feb 06 12:51:26 c2s159cf90 info Client disconnected: ssl handshake failed
...
Services
prosody.log:
12:42:16 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/localhost.crt': Check that the path is correct, and the file exists
Restart service
service prosody restart
Now error messages should not appear in the log on start prosody service.
jitsi-videobridge
In case of any errors check ssl certificates, configuration files /etc/jitsi/videobridge, etc.
jicofo
service jicofo start
prosody.log:
Feb 06 13:01:22 c2s16fd840 info Client connected
Feb 06 13:01:22 jcp1703190 info Incoming Jabber component connection
Feb 06 13:01:22 focus.qqq.com:component info External component successfully authenticated
Feb 06 13:01:23 c2s16fd840 info Client disconnected: ssl handshake failed
Feb 06 13:01:28 c2s160f660 info Client connected
Feb 06 13:01:28 c2s160f660 info Client disconnected: ssl handshake failed
Feb 06 13:01:28 c2s160b260 info Client connected
Feb 06 13:01:28 c2s160b260 info Client disconnected: ssl handshake failed
Apply the workaround below (or find another solution to the problem):
Add line org.jitsi.jicofo.ALWAYS_TRUST_MODE_ENABLED=true in /etc/jitsi/jicofo/sip-
communicator.properties configuration file.
Restart jicofo:
service jicofo restart
prosody.log should look like below:
Feb 06 13:08:58 c2s17ec910 info Client connected
Feb 06 13:08:58 jcp17c66a0 info Incoming Jabber component connection
Feb 06 13:08:58 focus.qqq.com:component info External component successfully authenticated
Feb 06 13:08:58 c2s17ec910 info Authenticated as focus@auth.qqq.com
On each new connection the messages like below should appear in prosody.log:
Feb 06 13:10:22 mod_bosh info New BOSH session, assigned it sid '55ffc51d-ab44-4328-9153-1a8bb2b1f34c'
Feb 06 13:10:22 bosh55ffc51d-ab44-4328-9153-1a8bb2b1f34c info Authenticated as c39d916b-81e4-4b17-820c-4b3485738403@qqq.com
Let's assume that port 5555 is free, and we will use it to access jitisi web content.
<IfModule mod_gnutls.c>
Listen 443
Listen 5555
</IfModule>
Apache2 configuration file qqq.com.conf has been added during jitsi setup and contains settings for jitsi web
content. Change 443 port to 5555 in /etc/apache2/sites-available/qqq.com.conf:
...
<VirtualHost *:5555>
ServerName qqq.com
...