I’ve been seeing this situation in which after someone leaves a room it still ‘remains present’ but it is actually not there, and so, if the same person reconnects, then it appears duplicated.
Has someone ever seen something like this?
It started happening a few days back, it did not happen before, i did no other changes other than the maximmum alocated ram for jvb and jicofo.
As far as I know, we always -and strongly- recommend using Google Chrome or Chromium-based browers; most of them use Google’s. When it fails, we recommend to use the app.
It has happened randomly in both scenarios, app and computer w/ chrome.
We do experience the same issue. Sometimes our users use a room in the span of several days and as a result there are sometimes 5-6 ghosts just hanging around and one of them is the room admin, so we cant even kick out those ghosts.
These ghosts are usually appearing after a user is being disconnected (mobile or browser) without explicitly leaving the room.
We have a vanilla/quick install on Ubuntu 18.04 installation.
sudo dpkg -l | grep -i jitsi
ii jicofo 1.0-508-1 amd64 JItsi Meet COnference FOcus
ii jigasi 1.1-38-g8f3c241-1 amd64 Jitsi Gateway for SIP
ii jitsi-meet 1.0.4101-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.3729-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-web 1.0.3729-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.3729-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge 1126-1 amd64 WebRTC compatible Selective Forwarding Unit (SFU)
Please let us know if we can help you with debugging.
I have seen that one time too with Jitsi Android (bad 3G connection). Out of curiosity, when you have the problem, does a new user joining the room see these ghosts ?
In testenvironment (“me” and “second me”) - once happened, now after each room creation (from RocketChat) a new one… Ofcourse not kickable, because all “moderators”.
The prosody storage is set to « memory », the secure domain is set.
Apache is used (not nginx)
We have around 700 participants at the same time on 4 jvb2 when it occurs and we used chat and sharing into the « bugged » rooms (don’t know if it is a pattern)
I was about to open a new post then I found this post seems describing my issue.
I found if the jitsi client (browser, desktop applications) closed abnormally (for example on Windows Ctrl+Alt+del then end jitsi by killing the process, or the participants disconnect because of poor connection), that user will stay in the room forever. Next time I enter the same room, the previous me is there and I can’t kick it out because the current me is not the host. I can replicate the issue on meet.jit.si as well.
Yeah I got the users out of the rooms by going to
/usr/share/jitsi-meet/interface_config.js
and disabling the recent list features.
Then restart.
This deletes all existing rooms (they are automatically re-created when you go to the URL, so no worries) and resets everything.
I no longer see ghost users when I re-enter a room for a new meeting in the same room some days later. Still, when the connection gets lost and a user reconnects during the same meeting, the old user is still in the meeting. So it’s not a perfect solution but better than beforehand.