Jitsi.meet container ... first touch - preparation for a final Resource description
- Thread starter jeyare
- Start date
- Latest activity Latest activity:
- Replies 37
- Views 7,120
Currently reading
Jitsi.meet container ... first touch - preparation for a final Resource description
Started playing with this today.
In short, everything works fine in LAN with multiple users but as soon as I have an outside connection, within 30sec or so all parties are DCed.
As instructed in the documentation if one is behind a NAT there needs to be a configuration of sip-communicator.properties file with these parameters:
I have tried it and still no joy. Even with static WAN IP or fqdn (logs show that mapping is correct).
My guess is that its still a firewall problem on some level, just not sure where I have tested it all and opened up (even turned off) all firewall rules but the problem still remains.
Will need to dig deeper into this.
In short, everything works fine in LAN with multiple users but as soon as I have an outside connection, within 30sec or so all parties are DCed.
As instructed in the documentation if one is behind a NAT there needs to be a configuration of sip-communicator.properties file with these parameters:
Code:
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=LAN IP
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=PUBLIC IPI have tried it and still no joy. Even with static WAN IP or fqdn (logs show that mapping is correct).
My guess is that its still a firewall problem on some level, just not sure where I have tested it all and opened up (even turned off) all firewall rules but the problem still remains.
Will need to dig deeper into this.
- 4
- 0
Hello mate,
I'm pretty sure your main issue is that you didn't enable websocket on your reverse proxy. Please let us know if it changes anything.
If you're not too sure how to do it, you can refer to that for instance on Synology NASes:
GitHub - orobardet/dsm-reverse-proxy-websocket: Configuration fix for Synology DSM 6 reverse proxy to handle websocket
Configuration fix for Synology DSM 6 reverse proxy to handle websocket - GitHub - orobardet/dsm-reverse-proxy-websocket: Configuration fix for Synology DSM 6 reverse proxy to handle websocket
github.com
Happy hacking!
Cheers
- 2,486
- 839
- NAS
- Synology, TrueNAS
- Operating system
- Linux
- Windows
@YouKnowWho
the recommendation (link) provided by you was great till 2018, but from DSM 6.2.1 is not needed anymore, because you can enable the WS in RP directly from APPPortal settings.
but thank you for your interest.
the recommendation (link) provided by you was great till 2018, but from DSM 6.2.1 is not needed anymore, because you can enable the WS in RP directly from APPPortal settings.
but thank you for your interest.
- 4
- 0
Did you enable it? It's not enabled by default, you need to setup a profile.
- 4
- 0
So to be 100% clear:
- your reverse HTTP proxy is the one managed by DSM on your Synology
- on the forward you've setup towards the jitsi container on the reverse proxy, you've activated the "custom headers" and added the 2 automatic ones that are proposed when you click on websocket under the arrow next to "create"
- and yet you still face the same issue of "network errors" when you try to connect from a browser
Am I understanding this right?
- 4
- 0
Nope, I just wanted to make sure we didn't overlook anything in order to help you. You were mentionning containers in relation to the feature so I wanted to make sure.
I followed the usual tutorials as you did and faced the same issue as you. For me the clear solution with that and I never see it mentionned in tutorials so I thought I could help. Apparently I can't.
Good luck, I hope you'll find the solution to your issue.
I followed the usual tutorials as you did and faced the same issue as you. For me the clear solution with that and I never see it mentionned in tutorials so I thought I could help. Apparently I can't.
Good luck, I hope you'll find the solution to your issue.
- 1,036
- 428
Last edited:
Seems like finaly it's time to dig into this topic.
I wrote myself a bash wrapper to do the heavy lifting and helps to keep track on settings I actualy did myself.
what it does
- clone the git repo
- creates a copy of .env from the env.example
- generate passwords inside the .env
- replace variable declared as JITSI_ENV_ in myscript in the .env file
- generate all required bind folders on the host (taken from the docker-compose.yml)
All JITSI_ENV_ variables match their counterparts in the .env file - appart from the prefix...
In combination with exporting the variables into the shell, this allows a generic approach to replace content in the .env file.
I will continue to work on it from time to time, when I find time. I assume it's not impossible to tame this beast.
So far
I wrote myself a bash wrapper to do the heavy lifting and helps to keep track on settings I actualy did myself.
what it does
- clone the git repo
- creates a copy of .env from the env.example
- generate passwords inside the .env
- replace variable declared as JITSI_ENV_ in myscript in the .env file
- generate all required bind folders on the host (taken from the docker-compose.yml)
All JITSI_ENV_ variables match their counterparts in the .env file - appart from the prefix...
In combination with exporting the variables into the shell, this allows a generic approach to replace content in the .env file.
Code:
#/bin/bash -eux
jitsi_parent_dir=/volume1/docker/jitsi
jitsi_git_dir=${jitsi_parent_dir}/docker-jitsi-meet
export JITSI_ENV_CONFIG="${jitsi_parent_dir}/config"
export JITSI_ENV_HTTP_PORT=8000
export JITSI_ENV_HTTPS_PORT=9443
export JITSI_ENV_DOCKER_HOST_ADDRESS=192.168.200.18
export JITSI_ENV_TZ=Europe/Berlin
export JITSI_ENV_PUBLIC_URL=https://jitsi.test.de
export JITSI_ENV_ENABLE_AUTH=1
export JITSI_ENV_ENABLE_GUESTS=1
export JITSI_ENV_AUTH_TYPE=internal
pushd () {
command pushd "$@" > /dev/null
}
popd () {
command popd "$@" > /dev/null
}
create_parent_dir_if_not_exist (){
if [ ! -e "${jitsi_parent_dir}" ]; then
mkdir -p "${jitsi_parent_dir}"
echo "created jitsi parent dir: ${jitsi_parent_dir}"
fi
}
checkout_git_if_not_exists(){
if [ ! -e "${jitsi_git_dir}" ]; then
pushd "${jitsi_parent_dir}"
git clone https://github.com/jitsi/docker-jitsi-meet.git
echo "cloned jitsi github project"
popd
fi
}
copy_env_if_not_exists(){
pushd "${jitsi_git_dir}"
if [ ! -e .env ];then
cp env.example .env
./gen-passwords.sh
echo "created .env file from env.example and generated password"
fi
popd
}
render_env(){
pushd "${jitsi_git_dir}"
variables=$(env | grep "JITSI_ENV_")
for var in ${variables}; do
raw_key=${var%=*}
key=${raw_key#JITSI_ENV_*}
value=${var#*=}
sed -i -E "s|#?${key}=.*|${key}=${value}|" .env
done
popd
}
create_config_dir_from_docker_compose(){
pushd "${jitsi_git_dir}"
mounts=$(grep '${CONFIG}' docker-compose.yml)
for mount in ${mounts};do
if [ "$mount" != "-" ];then
host_path=${mount%%:*}
host_path=${host_path#*/}
if [ ! -e "${JITSI_ENV_CONFIG}/${host_path}" ];then
mkdir -p "${JITSI_ENV_CONFIG}/${host_path}"
fi
fi
done
popd
}
create_parent_dir_if_not_exist
checkout_git_if_not_exists
copy_env_if_not_exists
render_env
create_config_dir_from_docker_composeI will continue to work on it from time to time, when I find time. I assume it's not impossible to tame this beast.
So far
docker-compose up brings it up, the ui can be accessed... but the connection get's lost. more to come in future posts...I've just managed to get this working!!! 
Using stable-5390-3
The HUGE trick for me was adding:
networks:
meet.jitsi:
ipam:
driver: default
config:
- subnet: 172.20.0.0/16
The 4 lines of code in bold to the end of the docker-compose.yml. It was my NAS firewall causing some of the problems
Didn't touch nginx (I'm using SWAG).
Other than that, moving the jitsi config folder, specifying the server name and LAN IP. Port forwarding I included 10000 which was the other specified port. The enabling auth, guest and internal auth.. Pretty much all as in OP.
Using stable-5390-3
The HUGE trick for me was adding:
networks:
meet.jitsi:
ipam:
driver: default
config:
- subnet: 172.20.0.0/16
The 4 lines of code in bold to the end of the docker-compose.yml. It was my NAS firewall causing some of the problems
Didn't touch nginx (I'm using SWAG).
Other than that, moving the jitsi config folder, specifying the server name and LAN IP. Port forwarding I included 10000 which was the other specified port. The enabling auth, guest and internal auth.. Pretty much all as in OP.
- 2,486
- 839
- NAS
- Synology, TrueNAS
- Operating system
- Linux
- Windows
@Akira
to be sure and exactly precise:
1. your link provided is targeted to your LAN IP address . Doesn’t matter. Here is the official link:
2. your solution is based on custom tune of the docker-compose.yml
but:
- you don’t mention the exact part of the .yml
- there you can find 5x definition of the meets.jitsi/network variables for each of the images included
it makes sense to define same subnet between the cooperated containers by this way, but it can be defined by portrainer network settings also.
So, what part of the yml was changed?
to be sure and exactly precise:
1. your link provided is targeted to your LAN IP address
. Doesn’t matter. Here is the official link:
GitHub - jitsi/docker-jitsi-meet: Jitsi Meet on Docker
Jitsi Meet on Docker. Contribute to jitsi/docker-jitsi-meet development by creating an account on GitHub.
2. your solution is based on custom tune of the docker-compose.yml
but:
- you don’t mention the exact part of the .yml
- there you can find 5x definition of the meets.jitsi/network variables for each of the images included
it makes sense to define same subnet between the cooperated containers by this way, but it can be defined by portrainer network settings also.
So, what part of the yml was changed?
@jeyare
1) sorry about that (copied the text from portainer) link to the build I used:
github.com
2) Allow me to quote from above:
However I do see (upon re-reading everything multiple times (I'm also in the process of fixing 20 machines and haven't even had my first coffee for the day)) where you're lost.
It only has to be added to the final one, where it defines the network:
I hope that helps.
Basically it keeps creating a new network with a random subnet this forces it to a subnet we can control.
The firewall was blocking communication with anything on this random network (including internally to it) due to my firewall being locked down and it not being a "known" network.
By specifying the subnet and giving it the same permissions in the firewall as my main docker network that fixed pretty much everything for me.
1) sorry about that (copied the text from portainer) link to the build I used:
Release stable-5390-3: release · jitsi/docker-jitsi-meet
Jitsi Meet on Docker. Contribute to jitsi/docker-jitsi-meet development by creating an account on GitHub.
github.com
2) Allow me to quote from above:
So I'm pretty sure I did say what I changed in the docker-compose.ymlnetworks:
meet.jitsi:
ipam:
driver: default
config:
- subnet: 172.20.0.0/16
The 4 lines of code in bold to the end of the docker-compose.yml. It was my NAS firewall causing some of the problems
However I do see (upon re-reading everything multiple times (I'm also in the process of fixing 20 machines
and haven't even had my first coffee for the day)) where you're lost.It only has to be added to the final one, where it defines the network:
Code:
networks:
meet.jitsi:
aliases:
- jvb.meet.jitsi
# Custom network so all services can communicate using a FQDN
networks:
meet.jitsi:
ipam:
driver: default
config:
- subnet: 172.20.0.0/16Basically it keeps creating a new network with a random subnet this forces it to a subnet we can control.
The firewall was blocking communication with anything on this random network (including internally to it) due to my firewall being locked down and it not being a "known" network.
By specifying the subnet and giving it the same permissions in the firewall as my main docker network that fixed pretty much everything for me.
- 1,036
- 428
It has been some time in this tread. Meanwhile I stumpled accross the "Jitsi-Meet for Synology" beta package, which can be downloaded from Showcase details | Community Package Hub. Just add https://www.cphub.net/ as remote source and install the package. As far as I understood, it uses the docker images under hood. Thus, there should be no reason to bother with a manual setup anymore.
- 1,036
- 428
From my experience that isn't the case if you build the environment yourself, that said (if the package now works) it's a much bigger job to build the whole environment yourself and work out what's causing any issues you run into. Despite the fact it's remained unused since I built and tested it I'm still rather pleased I did the work.
Last edited:
HI,
I dont see a folder /.jitsi-meet-cfg/config ... /.jitsi-meet-cfg/config/ngnix
I dont see config folder
This is a log when I start container
And the setup of container
Can you help me check where is wrong?
Create an account or login to comment
You must be a member in order to leave a comment
Create account
Create an account on our community. It's easy!
Log in
Already have an account? Log in here.
Similar threads
Another test would be to SSH onto the NAS and attempt to 'curl' the URL.
You could install Portainer if...
To be precise the container needs bash (most only provide /bin/sh instead of /bin/bash). SSH is not...
- Solved
If you are still interested in learning it: If you know how to write bash scripts, it should be possible...
I have no idea what you are doing, but I just tested it based on the instructions of the guide you linked...
hey guys. After several hours of changing and resetting things, its working again. I have no idea what...
Root of this issue found;)
For unknown reason, the docker package on the first, failing DS, uses the...
True!
Still, there are certain containers that can be run on those machines as long as users are aware of...
Welcome to SynoForum.com!
SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.
Registration is free, easy and fast!
Trending threads
-
-
DS220+ not working using TPLINK ER605 and ASUS TUF AX4200
- Started by nelvash606
- Replies: 4
-
-
Question for others, and me in future... NAS HDD to SSD upgrade...- Started by Jan Janowski
- Replies: 2
-
-
Unable to Create Multiple Volumes on DS1621+ with SHR Raid
- Started by BigRichard67
- Replies: 17