START JITSI MEETING PRO
START JITSI MEETING PASSWORD

START JITSI MEETING PASSWORD

So – to create user ‘john’ with password ‘12345’ you would run: sudo prosodyctl register john 12345 To add users who can create video conferences in Jitsi, run the following command: OK – this is great…we now have authentication…but we’re forgetting something – users! Sudo systemctl restart jitsi-videobridge2 Now let’s restart our Jitsi services: sudo systemctl restart prosody sudo nano -w /etc/jitsi/jicofo/sip-communicator.propertiesĪdd a new line at the bottom of this file: .URL=XMPP:Īgain, substitute your own FQDN for. Next, we need to tell the Jicofo service to only allow requests from our ‘authenticated’ domain. Just below that line, after the comment, you should see a line that is commented out that starts with ‘anonymousdomain.’ Uncomment that line and add your FQDN with a ‘guest.’ in front of it like this: anonymousdomain: '', Under the ‘var config = [‘ section (right near the top of the file), you should already see a line that says domain: ‘’, (it’ll say your FQDN, not mine). Next we need to configure our newly created VirtualHost / anonymous domain in our config.js file: sudo nano -w /etc/jitsi/meet/ *** NOTE: The VirtualHost that we just created – – is only used for Jitsi internally – there is no need to create a separate DNS A record for that FQDN.ĬTRL+X followed by Y+ENTER to save and exit. Scroll to the bottom of the file and add these lines to create the new virtual host with the anonymous login method (use your own FQDN): VirtualHost '' This disables the anonymous authentication for the ‘main’ server host URL – however, we also need to create a new virtual host for our anonymous guests in order to facilitate their anonymous connections.

So, for our example, we want to edit: sudo nano -w /etc/prosody/conf.avail/.luaįind the line that says ‘VirtualHost “.” Underneath that line you’ll see another line that says: authentication = 'anonymous'Ĭhange that line to: authentication = 'internal_plain' These changes have to be made in the /etc/prosody/conf.avail/.cfg.lua file. The first thing we need to do is enable authentication on our main domain – for our example, our main domain was. Prosody is the name of the Jitsi component that handles authentication. That way, if you mess up your server going through these next steps, you can revert to the snapshot and not have to start the entire project over from scratch!

START JITSI MEETING PRO

PRO TIP: If you are following along with this post after you already set up Jitsi from my previous post, I would recommend taking a snapshot of your Vultr or Digital Ocean server at this point.

Start jitsi meeting