How to kick out stalled sessions?

Hi, just a quick update, initial test does seems like we are able to kick out of app crashed (simulated via killing jitsi app) almost immediately! Thank you.


Did you solve this problem? Could you share the steps to enable epoll network backend in prosody?


Kind of, if disconnection is proper, then no issue, but if disconnection due to app crashed, then it still take a while before the ghost user disappear. Prosody is standard setup I presume (our team member installed it), but we did upgrade to prosody 0.11.5.

you can refer to this link


Thanks for the info, do you also upgrade prosody version?

yup, current latest stable: 0.11.5

is there any method for upgrading prosody on a live server without disrupting the service?

Also curious on if it is possible to upgrade on a live server without disrupting the service.

That is not possible when using a single machine. You need a way to have several shards, install new one, test them and rotate them.

Am also faced this problem, my prosody version is 0.11.5, also enabled epoll but still one user in that session, session timer also running

Unfortunately, I’ve seen this happening a lot lately on Participants get an error, they automatically disconnect but the stalled session remains. Then they join again and are now in the session together with the previous stalled session. Interestingly, these stalled sessions all have “excellent connection” (green indicator in the upper left corner). Some remain for days and are especially nasty if you forget to kick them before the session ends (since the stalled session then becomes moderator and cannot be kicked anymore).
Any idea what could be causing these sessions to stall? Is it client side, server side or both?

@iGadget which prosody version are you using?

Unknown, I don’t own or run, I’m just using it. And since it’s a free service, they only provide ‘support’ through here. Any way for me as a user to get this info?

Well you can open two tabs, open the javascript console and filter messages with version and you should see some of the components versions.

But upgrading it is responsibility of those hosting it …

Ah great. I get:

  • Prosody 0.10.0
  • JiCoFo 1.0.549

I asume those are not the latest versions?

Yep, that is correct. We had reports for having those stalled sessions when using prosody 0.10.

Perfect, I’ll try to contact BIT and ask them to update. Hopefully these issues will then belong to the past. Thanks for the info!

Just spoke with support today and they insist they’re up-to-date with the packages available on . Yet today we ran into the issue again several times.

Did you refer to packages from a different repository?

What makes it even more confusing is that the package name (i.e. jitsi-meet-prosody_1.0.4127-1_all.deb) does not match the version number you’re using. What’s up with that?

What about the prosody version? It is not coming from, the jitsi-meet-prosody package is just a package configuring prosody to be used with jitsi-meet, it does not contain prosody itself.