You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an issue identical in just about every single respect -- including the logs -- to the issue #1003.
Containers appear to be timing out when attempting to connect to one another.
Specifically, none of the containers can connect to the prosody container.
Environment
I am running this on Synology (Debian Linux), DSM 7.2.1-69057 Update 3.
Releases and Outcomes
Further, I tried several releases going back to 2021:
stable-9364-1
stable-9258
stable-7439
stable-6726
The outcome is identical in each with minor differences in the logs (e.g., docker container IPs).
Again, my logs are materially (or fully) identical to the ones in the issue #1003.
Steps to Reproduce
Key notes
Just like the author of #1003, I followed the manual.
There are two differences:
I had to mkdir ~/.jitsi-meet-cfg/web/crontabs manually b/c docker complained Error response from daemon: Bind mount failed: '/var/services/homes/ivan-admin/.jitsi-meet-cfg/web/crontabs' does not exists
I had to sudo chmod 777 ~/.jitsi-meet-cfg/. Without this, I am greeted with a blank/black/gray window when I try to access the web UI.
Other notes
I tried both setting PUBLIC_URL and leaving it commented.
I tried both setting JVB_ADVERTISE_IPS (later releases) or DOCKER_HOST_ADDRESS (earlier releases) and leaving it commented.
Full set of commands
#E.g., for stable-6726
mkdir ~/jitsi
cd~/jitsi
wget https://api.github.com/repos/jitsi/docker-jitsi-meet/zipball/stable-6726
7z x stable-6726
mkdir -p ~/.jitsi-meet-cfg/{web,transcripts,prosody/config,prosody/prosody-plugins-custom,jicofo,jvb,jigasi,jibri}
# note: manually creating the crontabs directory
mkdir ~/.jitsi-meet-cfg/web/crontabs
# note: setting permissions to resolve issue w/ blank/black screen
sudo chmod 777 ~/.jitsi-meet-cfg/
cd ./jitsi-docker-jitsi-meet-16b15f3
cp env.example .env
./gen-passwords.sh
# setting ports to the desired values
sed -i 's/8000/7180/g' .env
sed -i 's/8443/7443/g' .env
The text was updated successfully, but these errors were encountered:
Overview
I have an issue identical in just about every single respect -- including the logs -- to the issue #1003.
Containers appear to be timing out when attempting to connect to one another.
Specifically, none of the containers can connect to the prosody container.
Environment
I am running this on Synology (Debian Linux), DSM 7.2.1-69057 Update 3.
Releases and Outcomes
Further, I tried several releases going back to 2021:
stable-9364-1
stable-9258
stable-7439
stable-6726
The outcome is identical in each with minor differences in the logs (e.g., docker container IPs).
Again, my logs are materially (or fully) identical to the ones in the issue #1003.
Steps to Reproduce
Key notes
Just like the author of #1003, I followed the manual.
There are two differences:
mkdir ~/.jitsi-meet-cfg/web/crontabs
manually b/c docker complainedError response from daemon: Bind mount failed: '/var/services/homes/ivan-admin/.jitsi-meet-cfg/web/crontabs' does not exists
sudo chmod 777 ~/.jitsi-meet-cfg/
. Without this, I am greeted with a blank/black/gray window when I try to access the web UI.Other notes
PUBLIC_URL
and leaving it commented.JVB_ADVERTISE_IPS
(later releases) orDOCKER_HOST_ADDRESS
(earlier releases) and leaving it commented.Full set of commands
The text was updated successfully, but these errors were encountered: