Self-hosting jitsi-meet-docker Inactive black screen issue

Inactive status black screen occurs on self-hosting jitsi-meet-docker server. I know the bandwidth of its own server is 1G.

jvb log: Info: The endpoint was paused due to insufficient bandwidth (bwe = 106848bps).

In the jitsi-meet server, the inactive state does not occur under the same client condition.

Then it seems to be a problem with the self-hosting jitsi-meet-docker server.
Does it have anything to do with jitsi’s server even using jitsi-meet-docker?

Are there any bandwidth related options in the .env or config file etc??

And I want to measure the bandwidth with iperf.
How can I proceed?

help me please.

image

And The iperf measurement result from the client temporary server to the self-hosting jitsi-meet-docker server is as follows.

But why does the inactive black screen occur?

Is the test method wrong?

What prosody version are you running?

I am using the stable-5870 version.

Prosody, not Jitsi

How to check it?

dpkg -s prosody | grep Version

[root@localhost docker-jitsi-meet]# dpkg -s prosody | grep Version
dpkg-query: package ‘prosody’ is not installed and no information is available

Does it have anything to do with the prosody version?

Please tell me a solution.

Nothing was installed other than the one that was done by looking at the Self-Hosting Guide.

parsody is very important for jitsi and you installed docker version so it will be inside your jitsi server container , please look inside of it
and also see below link

Any further help need just ping me
Thanks

dpkg -l "prosody*"

How do I apply it to docker?

Please tell me how to set it up.

And the bandwidth and inactive black screen phenomenon is because the TURN setup is not working?

[root@localhost ~]# dpkg -l “prosody*”
dpkg-query: no packages found matching prosody*

inside the container… Not on the host

inside the container ??

What criteria should I check for UDP or TCP when testing bandwidth?

i think its running
docker exec -it < container name> /bin/ bash
here container of parsody name you put and check his version

i think you are firewall may be creating problems so thats why setup your coturn server will be good for every condition
and also share your logs so i can see what’s problems there

[root@localhost ~]# docker exec -it dockerjitsimeet_prosody_1 /bin/bash
root@d9854f5fa1ed:/# dpkg -l “prosody*”
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±===================-================-============-=================================
ii prosody 0.11.9-1~buster1 amd64 Lightweight Jabber/XMPP server
un prosody-modules (no description available)
un prosody-xmpp-server (no description available)

If you change enableLayerSuspension: false → true in config.js, the phenomenon does not seem to appear. Need more testing, but is it related to enableLayerSuspension?