New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Containers time out when attempting to connect to the prosody container #1003
Comments
If anyone has any suggestions for ways I can further diagnose, I'd be happy to try. |
What do you see in docker network ? Also, can you docker inspect both containers? Are they in the same network? |
Note, I'm running these diagnostic commands from macOS. First, I've confirmed the issue is still present. Excerpted from
In addition, this is still reproducible:
Now, output from
Output from
Output from
Output from
Finally, in case this is of any interest:
|
Oh, and uh, just to ensure the images I'm using are the latest:
|
Okay, now I find I can't reproduce! Maybe the images I grabbed had a bug or something. After running that set of |
I am not certain that this was due to any fault in Jitsi Meet itself, so I am going to close this issue. Sorry about the inconvenience. |
No worries. Every once in a while I've had to prune the network due to molar problems, oh well. Happy it's working for you now. |
Hi, just in case anyone finds this, I ran into this issue with the I have no idea why this correlation exists but this did the trick for me. |
I am having an issue very similar to the original description in #682. Containers appear to be timing out when attempting to connect to one another. Specifically, none of the containers can connect to the prosody container. I can reproduce this issue by running the steps from the manual on both Synology (Debian Linux) and on macOS.
I first noticed the issue when I connected to the web instance from my browser. The behavior manifested as a 504 error connecting to the websocket. I then attempted a connection directly using
curl
:From the logs of the web container, I found these corresponding error logs:
I tried connecting from the
jvb
container as well, which also timed out:This container's also cycling due to connection issues:
Output from
docker-compose ps
:However, Prosody is successfully running:
And it can be connected to from outside the containers:
So it seems as if the containers are unable to talk to one another for some reason.
I have made no modifications to the
docker-compose.yml
file. To the.env
file I have made only the following modifications:Even without those modifications, I see the same result (on macOS and on Linux).
The text was updated successfully, but these errors were encountered: