[noob] Unable to get the docker image working

Hi.

Thanks for providing a docker image template. However, I am not able to make it working.

The setup:

Running the image on a dedicated server with public ip on eth0. Having apache2 as proxy for both http(s) ports.

After some dock exec -it <id> cat/etc/passwd I was able to set the right perms on some folder. For further references:

root@khiksistigma :) # ls -aln 
total 32
drwxr-xr-x  8 1000 1000 4096 oct.   5 17:26 .
drwxrwxr-x 10 1000 1000 4096 oct.   5 16:26 ..
drwx------  2  999 1000 4096 oct.   5 16:51 jicofo
drwx------  2  999 1000 4096 oct.   5 17:38 jvb
drwxr-xr-x  4 1000 1000 4096 oct.   5 16:51 meet
drwxr-xr-x  5  101  102 4096 oct.   5 16:51 prosody
drwxr-xr-x  2  101  102 4096 oct.   5 17:31 prosody_var
drwxr-xr-x  4    0    0 4096 oct.   5 17:15 web

After reading other issues, am not running docker as root. .env docker-compose.yml.txt As I had no idea which value tu setup on DOCKER_HOST_ADDRESS I put the public ip address.

the problem:

After the docker-compose up everything seems to be working fine. Not so much errors in logs. Opening a webpage on jitsi.nailyk.fr seems to be working. However, when someone attempt to open the same link to join, the both webpages crashes and the log display SEVERE: Can not invite participant -- no bridge available.

Here is the list of opened ports:

CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS                                                                                            NAMES
d97e2e1f4afa        jitsi/jvb                   "/init"                  5 seconds ago       Up 4 seconds        51.15.17.68:10000->10000/udp                                                                     docker-jitsi-meet_jvb_1_f812e25b8c76
a10386ce5886        jitsi/prosody               "/init"                  23 minutes ago      Up 3 seconds        5222/tcp, 5269/tcp, 5280-5281/tcp, 5347/tcp                                                      docker-jitsi-meet_prosody_1_740326e9447f
f5de03020013        jitsi/web                   "/init"                  33 minutes ago      Up 3 seconds        127.0.0.1:8000->80/tcp, 127.0.0.1:8443->443/tcp                                                  docker-jitsi-meet_web_1_1f78696201e1
7a11218fe595        jitsi/jicofo                "/init"                  About an hour ago   Up 4 seconds                                                                                                         docker-jitsi-meet_jicofo_1_a4c262113f25

[...]

udp        0      0 51.15.17.68:10000       0.0.0.0:*                           27351/docker-proxy  

so only 10000 is publicly exposed but doesn’t seems to be open:

root@khiksistigma 1 :( # nc localhost 10000 -vvvv
localhost [127.0.0.1] 10000 (webmin) : Connection refused
 sent 0, rcvd 0

I already tried to delete the whole generated files (${CONFIG})without any changes. Docker log from docker-compose up to two tabs on the same room: docker.log

What am I missing please? Thanks in advance!

[saghul]

Ok, I think I know what’s happening. You seem to be running old images. I noticed an error creating the /config/certs/ directory (in the prosody logs) which was fixed over 2 months ago. So, let’s try the following:

Stop and remove all your containers:

docker-compose stop
docker-compose rm
docker network prune

Remove the directory you specified in CONFIG.

Now let’s fetch the new images:

docker-compose pull

Re-create the env file:

cp env.example .env

Customize it to your liking.

Start the containers again:

docker-compose up

I hope it works now!

[nailyk-fr]

Sorry, meant, if I rollback the git tree to that commit, I encounter the issue again. Need to try another point too about 777 chmod on the ${CONFIG} folder.