VIDEO GUIDE ** How to Setup Jitsi in Docker with a Reverse Proxy **


67 posts in this topic Last Reply

Recommended Posts

When you do the make directories step.  This is the command posted:

mkdir -p /mnt/user/appdata/jitsi/jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody,jicofo,jvb,jigasi,jibri}

 

With the letsencrypt docker changing to swag... does the word letsencrypt in the command have to be changed to swag?

Link to post
  • 1 month later...
  • Replies 66
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

How to install the Jitsi stack and run through a reverse proxy. This guide uses docker compose and portainer.      

I'm no pro, but here's how I'm doing updates. You will need docker-compose, so get it as is shown in the video or via nerd tools   1) Get and replace (appdata/jitsi/github/docker-jitsi-meet)

Try prosodyctl deluser username

Posted Images

On 10/31/2020 at 12:35 PM, Mogo said:

When you do the make directories step.  This is the command posted:

mkdir -p /mnt/user/appdata/jitsi/jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody,jicofo,jvb,jigasi,jibri}

 

With the letsencrypt docker changing to swag... does the word letsencrypt in the command have to be changed to swag?

I would like to know this too. If someone set's up a new Jitsi container then this should be clarified. Hope somebody can answer this? Thanks.

Link to post
On 10/31/2020 at 12:35 PM, Mogo said:

When you do the make directories step.  This is the command posted:

mkdir -p /mnt/user/appdata/jitsi/jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody,jicofo,jvb,jigasi,jibri}

 

With the letsencrypt docker changing to swag... does the word letsencrypt in the command have to be changed to swag?

I have checked on my live system and the web/letsencrypt folder exists and is empty. So perhaps it does not matter.

Link to post

Hi All,

 

i have found a recovery for my jitsi install when it became unusable after a update.

 

Broadly speaking all you have to do is follow SpaceinvaderOne's video and install jitsi again with a small change...

 

1. Backup your old jitsi install (/mnt/user/appdata/jitsi) or just rename the folder.

2. Remove the jisti containers using portainer (delete). The container stack will be recreated in the video guide.

3. Start following the video guide till 8:52, right after the git clone command to pulldown the docker.

4. Goto /appdata/jitsi/github/docker-jitsi-meet and open the docker-compose.yml file in a text editor.

5. Change the version of the docker container which is pulled for the installation to an older version! I used build 4416 which was released around the time when the installation video was posted.

Note: for reference goto: "https://hub.docker.com/search?q=jitsi&type=image"

Then search for jitsi, there is a tab called "Tag" that shows all available container build versions.

 

Modify the docker-compose.yml.

Within the file there are 4 sections corresponding to each container:

image: jitsi/prosody:latest

replace the part after image: with jitsi/prosody:4416

image: jitsi/jicofo:latest

replace the part after image: with jitsi/jicofo:4416

image: jitsi/jvb:latest

replace the part after image: with jitsi/jvb:4416

image: jitsi/web:latest

replace the part after image: with jitsi/web:4416

 

Once done, save the file and exit the editor.

 

6. Continue and finish the install following the guide in the video.

 

Hope that helps to recover broken installs. It worked for me.

Feel free to re-install and test any newer version of jitsi until your install breaks :)

The latest version as of today had issues for me...

 

Thanks.

 

 

 

 

 

 

 

Link to post
On 6/11/2020 at 5:56 PM, ChadwickTheCrab said:

 

I was having the same issue until I found a script here which I modified to work with SpaceInvader's tutorial and UnRaid. It required me to install bind and lmdb from the Nerd Tools plugin so that 'host' is installed. It sets and updates your public IP inside the sip-communicator.properties file. I have this as a user script running hourly. 

 


#!/bin/bash

#Domain that points to your public IP
DNSNAME="meet.changethistoyourdomain.com"

# get the actual IP from the Internet
IPint=$(host -tA $DNSNAME 8.8.8.8 | grep address | cut -d " " -f4 )

# get the configured IP of Jitsi
IPjitsi=$(grep 'NAT_HARVESTER_PUBLIC_ADDRESS' /mnt/user/appdata/jitsi/jitsi-meet-cfg/jvb/sip-communicator.properties |  grep -oE "[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+")

if [ "$IPjitsi" = "$IPint" ]
then
        echo "IP has not been changed!"
        exit 0
fi

#clear config
sed -i '/NAT_HARVESTER_PUBLIC_ADDRESS/d' /mnt/user/appdata/jitsi/jitsi-meet-cfg/jvb/sip-communicator.properties

#get IP and renew line
echo org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=$IPint >> /mnt/user/appdata/jitsi/jitsi-meet-cfg/jvb/sip-communicator.properties

#Restart jocofo
docker restart focus.meet.jitsi
#Restart video
docker restart video.meet.jitsi

 

seems like I have a problem with the persistent volumes of these dockers.

When using the script I wondered why the IP does not change and weird things happen.

But after trying to change  \jitsi\jitsi-meet-cfg\web\config.js from meet.jitsi I recognized, that each time a docker is restarted or even only stopped and started again via portainer, the config files are rewritten.

 

That's not normal behaviour, is it? 😅 

Link to post
On 12/28/2020 at 4:53 PM, Petty said:

Has anyone tried to enable recording and streaming as an addition to this? I'd love to add those features and was curious if someone's trudged through the muck of getting it working already. 

Same here, I'm trying to get jigasi working, but, I just can't... Has anyone tried ?

 

Thanks for reading.

Link to post

I followed the video and everything works so far. But when people join my meetings outside of my network sound and video doesn´t work. Any idea how to solve this?

 

 

SOLVED: I forgot the portforwarding.

Edited by antagon
Link to post
  • 2 weeks later...
On 1/26/2021 at 3:43 AM, antagon said:

After following the video I got it almost running. But whenever I open up my jitsi page that´s what I see:

Bildschirmfoto 2021-01-25 um 19.46.56.png

Same here. I'm running into the same issue.

Link to post
On 12/30/2020 at 1:48 PM, xPliZit_xs said:

Hi All,

 

i have found a recovery for my jitsi install when it became unusable after a update.

 

Broadly speaking all you have to do is follow SpaceinvaderOne's video and install jitsi again with a small change...

 

1. Backup your old jitsi install (/mnt/user/appdata/jitsi) or just rename the folder.

2. Remove the jisti containers using portainer (delete). The container stack will be recreated in the video guide.

3. Start following the video guide till 8:52, right after the git clone command to pulldown the docker.

4. Goto /appdata/jitsi/github/docker-jitsi-meet and open the docker-compose.yml file in a text editor.

5. Change the version of the docker container which is pulled for the installation to an older version! I used build 4416 which was released around the time when the installation video was posted.

Note: for reference goto: "https://hub.docker.com/search?q=jitsi&type=image"

Then search for jitsi, there is a tab called "Tag" that shows all available container build versions.

 

Modify the docker-compose.yml.

Within the file there are 4 sections corresponding to each container:

image: jitsi/prosody:latest

replace the part after image: with jitsi/prosody:4416

image: jitsi/jicofo:latest

replace the part after image: with jitsi/jicofo:4416

image: jitsi/jvb:latest

replace the part after image: with jitsi/jvb:4416

image: jitsi/web:latest

replace the part after image: with jitsi/web:4416

 

Once done, save the file and exit the editor.

 

6. Continue and finish the install following the guide in the video.

 

Hope that helps to recover broken installs. It worked for me.

Feel free to re-install and test any newer version of jitsi until your install breaks :)

The latest version as of today had issues for me...

 

Thanks.

 

 

 

 

 

 

 

Hey! Thanks so much for this post! I recently had to rebuild some stuff from scratch and this helped get my Jitsi service back online!

Link to post
  • 2 weeks later...
On 12/30/2020 at 7:48 PM, xPliZit_xs said:

Hi All,

 

i have found a recovery for my jitsi install when it became unusable after a update.

 

Broadly speaking all you have to do is follow SpaceinvaderOne's video and install jitsi again with a small change...

 

1. Backup your old jitsi install (/mnt/user/appdata/jitsi) or just rename the folder.

2. Remove the jisti containers using portainer (delete). The container stack will be recreated in the video guide.

3. Start following the video guide till 8:52, right after the git clone command to pulldown the docker.

4. Goto /appdata/jitsi/github/docker-jitsi-meet and open the docker-compose.yml file in a text editor.

5. Change the version of the docker container which is pulled for the installation to an older version! I used build 4416 which was released around the time when the installation video was posted.

Note: for reference goto: "https://hub.docker.com/search?q=jitsi&type=image"

Then search for jitsi, there is a tab called "Tag" that shows all available container build versions.

 

Modify the docker-compose.yml.

Within the file there are 4 sections corresponding to each container:

image: jitsi/prosody:latest

replace the part after image: with jitsi/prosody:4416

image: jitsi/jicofo:latest

replace the part after image: with jitsi/jicofo:4416

image: jitsi/jvb:latest

replace the part after image: with jitsi/jvb:4416

image: jitsi/web:latest

replace the part after image: with jitsi/web:4416

 

Once done, save the file and exit the editor.

 

6. Continue and finish the install following the guide in the video.

 

Hope that helps to recover broken installs. It worked for me.

Feel free to re-install and test any newer version of jitsi until your install breaks :)

The latest version as of today had issues for me...

 

Thanks.

 

 

 

 

 

 

 

 

 

Thanks for finding out the version numbers. I wonder if anyone got a newer version working? Looks like some cool new features. I been trying for 2 days without much luck.

Link to post

@markinsutton

 

i was able to get the latest version working but only if you did not "update" but just reinstall according to the video.

After the install i usually would get some kind of error/browser crash when connecting to the browser. In this case you would restart unraid server and after this jitsi would work.

I am running whatever is latest from about 1-2 month ago. So a new install seems to be ok but the update according to page 1 might break further updates and would not recommend trying this.

Stop jitsi contianers then uninstall old version by using portainer to remove jisti containers and rename old jisti folder in appdata as a "backup" in case you need it.

Then start new jitsi install from scratch.

When install is done reboot your server. Worked for me.

 

 

P.S. i had to use authentication as described in the step when the .env file is created  otherwise jitsi install would not work at all. 

 

Edited by xPliZit_xs
Link to post

Ok guys.... i could not resist and did a fresh install using the latest jitsi and it worked for me. Follow my REINSTALL guide below its (99.9% Spaceinvaderone with my own words)

 

Needless to say is that you have to have a working SWAG reverse PROXI.

 

REINSTALL GUIDE

Precondition: This tutorial requires that your letsencypt/SWAG reverse proxi works and your firewall forwarding ports are set correctly. 


UNINSTALL

1. open portainer and select the "stack" of jitsi containers. Select all 4 and stop and then click remove. In unraid web ui click stop on the displayed jitis container
2. open krusader and rename the existing jisti folder in appdata e.g. jitis_bak

INSTALL
1. Open terminal into UNRAID from web interface
2. Paste: curl -L "https://github.com/docker/compose/releases/download/1.25.5/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
3. sudo chmod +x /usr/local/bin/docker-compose
4. Install portainer if not already done (use video as in community applications from spaceinvader)
5. mkdir -p /mnt/user/appdata/jitsi/jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody,jicofo,jvb,jigasi,jibri} (press ENTER)
6. mkdir -p /mnt/user/appdata/jitsi/github && cd /mnt/user/appdata/jitsi/github (press ENTER)
7. git clone https://github.com/jitsi/docker-jitsi-meet && cd docker-jitsi-meet (press ENTER)
8. use nano to edit the .env file
-> enter: nano env.example (press ENTER)
-> leave the 6 passwords blank at the beginning of the file
-> edit location of the config from: CONFIG=~/.jitis-meet-cfg to: CONFIG=/mnt/user/appdata/jitsi/jitsi-meet-cfg/
-> edit timezone if needed (optional)
-> enable public URL for the web service (remove # in front of line) and then put YOUR full URL of your jitsi webservice under which user can reach jitsi
e.g. PUBLIC_URL=https://geocities.meetmeonjitsi.org
-> remove # from line "DOCKER_HOST_ADDRESS=192.168.1.1" and edit the IP to your current UNRAID IP address
DONT IGNORE the authentication part. USE Authentication
-> remove # from ENABLE_AUTH=1
-> remove # from ENABLE_GUESTS=1
-> remove # from AUTH_TYPE=internal
when using nano press CTRL+O then ENTER to write the file and CTRL+X to exit
9. cp env.example .env (press ENTER)
10. gen-passwords.sh (press ENTER)
11. docker-compose up -d    (press ENTER) Note: if you have done any install before then old jitisi containers may exist already and show up with _1 at the end of the name.
Unused old containers can be removed or pruned later.
12. login to portainer 
-> you will see 1 stack has been created
-> select it and click docker-jitsi-meet to see all four containers
use the video guide to see howto rename them.
Essentially assign proxynet to each container (join network), delete(leave network) the already existing network and rename the container as below for all 4:
- jicofo     -> focus.meet.jitsi
- jvb         ->    video.meet.jitsi
- prosody     ->    xmpp.meet.jitsi
- web         ->    meet.jitsi    

13. Assuming letsencrypt/SWAG is already running correctly then all the necessary files are in place
-> Stop SWAG, Start SWAG

14. open a console window into the container xmpp.meet.jitsi
in UNRAID dashboard left click on xmpp.meet.jitis container (running) and select console

USE as example: prosodyctl --config /config/prosody.cfg.lua register <<YOUR USERNAME>> meet.jitsi <<YOUR PASSWORD>>
PASTE (EXAMPLE): prosodyctl --config /config/prosody.cfg.lua register Johnny meet.jitsi PIW*$@$(J822189429
Press ENTER
Close the console
Restart xmpp.meet.jitsi container
(optional/untested: restart SWAG again. This may resolve that you have to restart unraid (untested))

15. Reboot UNRAID
16. TEST Jitsi

 

 

Just did this myself and worked correctly. If it not working for you then maybe there is an issue with your reverse proxi.

 

Thanks and Good Luck!

Edited by xPliZit_xs
Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.