Manual install on ubuntu 19.10

Sorry in advance but I tried to work my way around the 2 links filter for new users, since I think they’re very much relevant.

I’ve tried following jitsi.github .io/handbook/docs/devops-guide/devops-guide-manual but this is apparently very out of date, so I tried to make the best out of the debian install scripts, mainly this prosody example and the example configs, but at best I could do 1:1 confs over p2p anything that would require a turn server didn’t work and now somehow I can’t even do 1:1 any longer.


I want to run jitsi behind a nginx server that already has an le cert on the domain


I installed prosody, jitsi-videobridge2 and jicofo all via apt and git cloned jitsi/jitsi-meet to /opt/jitsi-meet/

this is my most recent config:

-- /etc/prosody/conf.d/
plugin_paths = { "/opt/jitsi-meet/resources/prosody-plugins" }

muc_mapper_domain_base = "";

cross_domain_bosh = false;
consider_bosh_secure = true;

turncredentials_secret = "redacted";

turncredentials = {
  { type = "stun", host = "", port = "3748" },
  { type = "turn", host = "", port = "3748", transport = "udp" },
  { type = "turn", host = "", port = "3478", transport = "tcp" },
  { type = "turns", host = "", port = "5349", transport = "udp" },
  { type = "turns", host = "", port = "5349", transport = "tcp" }

-- ssl = {
--   protocol = "tlsv1_2+";
-- }

VirtualHost ""
    authentication = "anonymous"
    ssl = {
        key = "/var/lib/prosody/";
        certificate = "/var/lib/prosody/";
    c2s_require_encryption = false
    speakerstats_component = ""
    conference_duration_component = ""
    -- we need bosh
    modules_enabled = {
        "ping"; -- Enable mod_ping
    lobby_muc = ""
    main_muc = ""

-- Component ""
--     component_secret = "VQoDKTViBy8Dmir6rULk"

Component "" "muc"
    storage = "memory"
    modules_enabled = {
        -- "token_verification";
    admins = { "" }
    muc_room_locking = false
    muc_room_default_public_jids = true

-- internal muc component
Component "" "muc"
    ssl = {
        key = "/var/lib/prosody/";
        certificate = "/var/lib/prosody/";
    storage = "memory"
    modules_enabled = {
    admins = { "", "" }
    muc_room_locking = false
    muc_room_default_public_jids = true

VirtualHost ""
    authentication = "internal_plain"

Component ""
    component_secret = "njpVCF6T9a6d9TGmLVHQ"

Component "" "speakerstats_component"
    muc_component = ""

Component "" "conference_duration_component"
    muc_component = ""

Component "" "muc"
    storage = "memory"
    restrict_room_creation = false
    muc_room_locking = false
    muc_room_default_public_jids = true                                           

I then generated self signed certs (not exactly sure what requires self signed certs here? ideally, since everything is behind a reverse proxy and this is just internal communciation, I would just not use tls at all) for everything here and tried to symlink /var/lib/prosody/ /usr/local/share/ca-certificates/

and I also tried just and both internal.auth and auth.
After symlinking I always run:

sudo update-ca-certificates -f
sudo prosodyctl register focus 936has8HF3VnkN9C84Z5
sudo prosodyctl restart

My JICONFO conf:

# sets the host name of the XMPP server

# sets the XMPP domain (default: none)

# sets the secret used to authenticate as an XMPP component

# sets the port to use for the XMPP component connection

# sets the XMPP domain name to use for XMPP user logins

# sets the username to use for XMPP user logins

# sets the password to use for XMPP user logins

# extra options to pass to the jicofo daemon

# adds java system props that are passed to jicofo (default are for home and logging config file)
JAVA_SYS_PROPS=" -Djava.util.logging.config.file=/etc/jitsi/jicofo/logging.propertie"

and my videobridge config:

# Jitsi Videobridge settings

# sets the XMPP domain (default: none)

# sets the hostname of the XMPP server (default: domain if set, localhost otherwise)

# sets the port of the XMPP server (default: 5275)

# sets the shared secret used to authenticate to the XMPP server

# extra options to pass to the JVB daemon

# adds java system props that are passed to jvb (default are for home and logging config file)
JAVA_SYS_PROPS=" -Djava.util.logging.config.file=/etc/jitsi/videobridge/"

my nginx config I am fairly sure works since it worked with the quickinstall guide:

server {
        listen [::]:443 ssl http2;
        listen 443 ssl http2;

        include snippets/;
        include snippets/robots.conf;

        root /opt/jitsi-meet;
        index index.html index.htm;
        error_page 404 /static/404.html;

        location ~ ^/([a-zA-Z0-9=\?]+)$ {
                rewrite ^/(.*)$ / break;

        location / {
                ssi on;

        # BOSH
        location /http-bind {
                proxy_pass              http://localhost:5280/http-bind;
                proxy_set_header        X-Forwarded-For $remote_addr;
                proxy_set_header        Host $http_host;

        # xmpp websockets
        location /xmpp-websocket {
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                proxy_set_header Host $host;
                tcp_nodelay on;

and my config.js looks like this:

var config = {
    // Connection

    hosts: {
        // XMPP domain.
        domain: '',

        // When using authentication, domain for guest users.
        // anonymousdomain: '',

        // Domain for authenticated users. Defaults to <domain>.
        // authdomain: '',

        // Jirecon recording component domain.
        // jirecon: '',

        // Call control component (Jigasi).
        // call_control: '',

        // Focus component domain. Defaults to focus.<domain>.
        focus: '',
        bridge: '',

        // XMPP MUC domain. FIXME: use XEP-0030 to discover it.
        muc: ''

    // BOSH URL. FIXME: use XEP-0156 to discover it.
    bosh: '//',
//... the rest is exactly like

I definitely think something with the videobridge is misconfigured since the secret isn’t being used anywhere, but the newer examples all don’t use jitsi-videobridge.jitsi.JVB_HOSTNAME anywhere?

Additionally I opened up these ports for jitsi:

  • 10000/udp
  • 4443/tcp
    and additionally for turn
  • 49152:65535/udp
  • 5349/udp
  • 5349/tcp
  • 3478/tcp
  • 3478/udp

and of course 80/443 for https? and 20 for ssh.


prosody mainly seems to have trouble connecting to focus.jitsi:
Jun 30 14:25:53 warn Component not connected, bouncing error for: <iq type='get' from='' id='1lXFD-33' to=''>

also the error log keeps telling me:
Jun 30 14:25:33 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

But someone in the forums claims this can be ignored?

jicovo complains about XMPP error reply received from pretty every component
the domains here are correct though

videobridge says community.jitsi. org/t/saslerror-using-scram-sha-1-not-authorized-on-debian-buster-system-with-existing-prosody/26775 which I get since I definitely am not setting the videobridge secret correctly.

I am 99% sure my turn servers work cos they seem to work with my matrix instance, but I also tried using the default jitsi stun/turn servers and also respond well to webrtc.github. io/samples/src/content/peerconnection/trickle-ice/

I realize that using the quick-install is recommended and I did have that working for sometime, but it’s very frustrating when I update my system that jitsi always destroys both my turnserver and nginx and I would rather administrate my configs myself if possible.

Thank you very much for your help!