
# prosodyctl -root cert import /etc/letsencrypt/live If you use certbot, you can import the certificate with: You need now to generate the certificate for JITSIFQDN and auth. JITSIFQDN.crt" Īuthentication = "internal_plain" /etc/prosody/conf.d/ - Proxy to jicofo's user JID, so that it does not have to register as a component.Ĭomponent "focus. JITSIFQDN.key" Ĭertificate = "/etc/prosody/certs/auth. Key = "/etc/prosody/certs/ JITSIFQDN.key" Ĭertificate = "/etc/prosody/certs/ JITSIFQDN.crt" replace all occurences of focusUser by focus etc/prosody/conf.d/ - replace all occurences of by JITSIFQDN # cp /usr/share/doc/jitsi-meet-prosody/ conf.d/ The package jitsi-meet-prosody AUR provides a configuration you can easily customize:
#Jitsi ports install
The rest of the prosody configuration assumes you have a local install of prosody. If you do not already have a prosody server set up, install prosody and lua52-sec now. Prosody is a prerequisite and you will need to add a configuration to it for your Jitsi services. It works even if your domain is behind a proxy like Cloudflare which does not return the real ip of the server. Let us jitsi-meet components reach each other with local ip. usr/share/doc/jitsi-meet-turnserver-nightly Make sure to use different and safe passwords! Configuration paths Package Passwords should be obtained in a safe way, e.g.
#Jitsi ports how to
The remainder assumes that you have done this.Īlso you should have SSL/TLS certificates for your domain, on how to obtain free certificates see certbot.
#Jitsi ports update
You will need to update DNS record for your server with an entry of your chosen subdomain, in the above example meet. It is however strongly encouraged from security standpoint to host webapps on their own subdomain. If your server name is then a common choice for your jitsi will be, but you can choose freely. Refer to the Jitsi philosophy for rationale. Note: This configuration yields an open server for everyone to connect. You need those optionals packages to run a standalone server: #NoExtract = usr/share/gtk-doc/html/* usr/share/doc/* Some packages install configuration examples in /usr/share/doc, ensure to comment this line in /etc/nf: nightly and nightly-bin can not be installed at the same time, but stable and nightly can be). The bin one conflicts with the normal version (i.e. You need to choose between the normal or the bin version. It is possible to install them at the same time, but you will need to use separate port and several instances of prosody (the plugins cannot be scope by virtual host). You can either use the git versions, the nightly version or the stable versions.

