Jitsi.meet container ... first touch - preparation for a final Resource description

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:

Code:
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=LAN IP
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=PUBLIC IP

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.
 
Docker image:
jitsi/web
483MB

Launch:
jitsi-web1

Advanced settings:
Auto restart - enabled

NAS Docker Parent folder:
docker/jitsi
create .env folder
copy env.example into .env (you need download this file from GitHub - official Jitsi)

Edit the env.example file
1. change the line:
# Directory where all configuration will be stored
from CONFIG=~/.jitsi-meet-cfg
to CONFIG=/volume1/docker/jitsi/.jitsi-meet-cfg

2.Enable authentication, guest access and internal authentication:
ENABLE_AUTH=1
ENABLE_GUESTS=1
AUTH_TYPE=internal

3. Setup your FDQN for the jitsi + docker host address:
PUBLIC_URL=https://meet.domain.com
don't forget to manage your DNS record
DOCKER_HOST_ADDRESS=your NAS LAN ADDRESS

4. Auth. config lines:
# Enable authentication
ENABLE_AUTH=1
# Enable guest access
ENABLE_GUESTS=1
# Select authentication type: internal, jwt or ldap
AUTH_TYPE=internal


NAS side Volume preparation:
NAS folder: docker/jitsi
make new subfolders:
/.env
/config
/.jitsi-meet-cfg ....... in this subfolder make next structure by SSH command:
mkdir -p -v /volume1/docker/jitsi/.jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody/config,prosody/prosody-plugins-custom,jicofo,jvb,jigasi,jibri}
View attachment 1917
Volume setup for in Docker (NAS ... Image):
/.env ... /.env
/.jitsi-meet-cfg ... /.jitsi-meet-cfg
/.jitsi-meet-cfg/config ... /.jitsi-meet-cfg/config/ngnix
in the folder:
/.jitsi-meet-cfg/config/ngnix
you will find file
you need to note (#) lines 33-38 (reason of errors of ngnix, then solved):
# BOSH
#location = /http-bind {
# proxy_pass <no value>/http-bind;
# proxy_set_header X-Forwarded-For $remote_addr;
# proxy_set_header Host <no value>;
#}


Ports:
your NAS port / 443 TCP
your NAS port / 80 TCP
your NAS port / 4443 TCP

Environments:
TZ: up to you..... List of tz database time zones - Wikipedia
CONFIG: /.jitsi-meet-cfg
no need more, because everything is defined by file in: /volume1/docker/jitsi/.jitsi-meet-cfg

Setup of NAS Firewall + RP
then:

and done

View attachment 1918

you can setup your devices in right upper corner icon

then you just need to "Start a new meeting"
done, meeting was established and started. Perfect.

and here is my cyclic "disconnecting":
View attachment 1919

Jitsi container Console:
- no error found in log
- copy of the log:
,[cont-finish.d] executing container finish scripts...
,[cont-finish.d] done.
,[s6-finish] waiting for services.
,[s6-finish] sending all processes the TERM signal.
,[s6-finish] sending all processes the KILL signal and exiting.
,[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
,[s6-init] ensuring user provided files have correct perms...exited 0.
,[fix-attrs.d] applying ownership & permissions fixes...
,[fix-attrs.d] done.
,[cont-init.d] executing container initialization scripts...
,[cont-init.d] 01-set-timezone: executing...
,[cont-init.d] 01-set-timezone: exited 0.
,[cont-init.d] 10-config: executing...
,using keys found in /config/keys
,[cont-init.d] 10-config: exited 0.
,[cont-init.d] done.
,[services.d] starting services
,[services.d] done.
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET / HTTP/1.1" 200 15397 "-" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /Test HTTP/1.1" 200 15397 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:33 +0200] "POST /http-bind?room=test HTTP/1.1" 405 580 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /Test HTTP/1.1" 200 15397 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:50 +0200] "POST /http-bind?room=test HTTP/1.1" 405 580 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /Test HTTP/1.1" 200 15397 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:07 +0200] "POST /http-bind?room=test HTTP/1.1" 405 580 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,
,


Now:
tested image jitsi/prosody
for a possible "unregistered user" issue ... but guest connection is enabled in jitsi

Searched over internet - tons of similar issues, no single right solution
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:
Even if you don't have a Synology or Nginx, that should guide you well in terms of what to try next.
Happy hacking!
Cheers
 
@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.
 
for me it's one of the basic feature for my 20+ containers
so we can speak deeply about DSM if you wish
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?
 
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.
 
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.

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_compose

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 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!!! :D
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 :D

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.
 
@Akira
to be sure and exactly precise:

1. your link provided is targeted to your LAN IP address :cool: . 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?
 
@jeyare
1) sorry about that (copied the text from portainer) link to the build I used:

2) Allow me to quote from above:

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 :D
So I'm pretty sure I did say what I changed in the docker-compose.yml ;)
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/16
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.
 
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:
Docker image:
jitsi/web
483MB

Launch:
jitsi-web1

Advanced settings:
Auto restart - enabled

NAS Docker Parent folder:
docker/jitsi
create .env folder
copy env.example into .env (you need download this file from GitHub - official Jitsi)

Edit the env.example file
1. change the line:
# Directory where all configuration will be stored
from CONFIG=~/.jitsi-meet-cfg
to CONFIG=/volume1/docker/jitsi/.jitsi-meet-cfg

2.Enable authentication, guest access and internal authentication:
ENABLE_AUTH=1
ENABLE_GUESTS=1
AUTH_TYPE=internal

3. Setup your FDQN for the jitsi + docker host address:
PUBLIC_URL=https://meet.domain.com
don't forget to manage your DNS record
DOCKER_HOST_ADDRESS=your NAS LAN ADDRESS

4. Auth. config lines:
# Enable authentication
ENABLE_AUTH=1
# Enable guest access
ENABLE_GUESTS=1
# Select authentication type: internal, jwt or ldap
AUTH_TYPE=internal


NAS side Volume preparation:
NAS folder: docker/jitsi
make new subfolders:
/.env
/config
/.jitsi-meet-cfg ....... in this subfolder make next structure by SSH command:
mkdir -p -v /volume1/docker/jitsi/.jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody/config,prosody/prosody-plugins-custom,jicofo,jvb,jigasi,jibri}
View attachment 1917
Volume setup for in Docker (NAS ... Image):
/.env ... /.env
/.jitsi-meet-cfg ... /.jitsi-meet-cfg
/.jitsi-meet-cfg/config ... /.jitsi-meet-cfg/config/ngnix
in the folder:
/.jitsi-meet-cfg/config/ngnix
you will find file
you need to note (#) lines 33-38 (reason of errors of ngnix, then solved):
# BOSH
#location = /http-bind {
# proxy_pass <no value>/http-bind;
# proxy_set_header X-Forwarded-For $remote_addr;
# proxy_set_header Host <no value>;
#}


Ports:
your NAS port / 443 TCP
your NAS port / 80 TCP
your NAS port / 4443 TCP

Environments:
TZ: up to you..... List of tz database time zones - Wikipedia
CONFIG: /.jitsi-meet-cfg
no need more, because everything is defined by file in: /volume1/docker/jitsi/.jitsi-meet-cfg

Setup of NAS Firewall + RP
then:

and done

View attachment 1918

you can setup your devices in right upper corner icon

then you just need to "Start a new meeting"
done, meeting was established and started. Perfect.

and here is my cyclic "disconnecting":
View attachment 1919

Jitsi container Console:
- no error found in log
- copy of the log:
,[cont-finish.d] executing container finish scripts...
,[cont-finish.d] done.
,[s6-finish] waiting for services.
,[s6-finish] sending all processes the TERM signal.
,[s6-finish] sending all processes the KILL signal and exiting.
,[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
,[s6-init] ensuring user provided files have correct perms...exited 0.
,[fix-attrs.d] applying ownership & permissions fixes...
,[fix-attrs.d] done.
,[cont-init.d] executing container initialization scripts...
,[cont-init.d] 01-set-timezone: executing...
,[cont-init.d] 01-set-timezone: exited 0.
,[cont-init.d] 10-config: executing...
,using keys found in /config/keys
,[cont-init.d] 10-config: exited 0.
,[cont-init.d] done.
,[services.d] starting services
,[services.d] done.
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET / HTTP/1.1" 200 15397 "-" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:27 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /Test HTTP/1.1" 200 15397 "https://xx.xx.com/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:32 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:33 +0200] "POST /http-bind?room=test HTTP/1.1" 405 580 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /Test HTTP/1.1" 200 15397 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:49 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:15:50 +0200] "POST /http-bind?room=test HTTP/1.1" 405 580 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /Test HTTP/1.1" 200 15397 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /libs/do_external_connect.min.js?v=1 HTTP/1.1" 200 1173 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /libs/lib-jitsi-meet.min.js?v=4289 HTTP/1.1" 200 228097 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:06 +0200] "GET /libs/app.bundle.min.js?v=4289 HTTP/1.1" 200 1345461 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,172.17.0.1 - - [08/Aug/2020:20:16:07 +0200] "POST /http-bind?room=test HTTP/1.1" 405 580 "https://xx.xx.com/Test" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36"
,
,


Now:
tested image jitsi/prosody
for a possible "unregistered user" issue ... but guest connection is enabled in jitsi

Searched over internet - tons of similar issues, no single right solution
HI,
I dont see a folder /.jitsi-meet-cfg/config ... /.jitsi-meet-cfg/config/ngnix
I dont see config folder
1627216422467.png

1627216441693.png

This is a log when I start container
1627216545249.png

And the setup of container
1627216594534.png

1627216611419.png

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 aspect that might indicate it is that the swarm mode finally works! It is the first Synology...
Replies
4
Views
923
Sorry, I read your post late. You already did it. Thanks,
Replies
3
Views
989
I can’t find any option to restore just the settings. 1710356648 Phew, managed to fix it. Within the...
Replies
4
Views
711
  • Question
Open an issue on that GitHub page. The developers will be glad to assist. OP has posted two threads on...
Replies
5
Views
1,354
I'm happy with email notifications but in v0.3.3 of dockcheck the author added apprise notifications...
Replies
4
Views
1,644
Hi, I'll start by saying, my understanding of networking is very limited so I apologize if I'm asking an...
Replies
0
Views
893
You can run cmd.exe to get a command window from which you can execute SSH commands. However, my personal...
Replies
36
Views
4,115

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top