Multiple Frozen User Displays

Hi,
Over recent days I have opened a room on my secure Ubuntu LTS server.
On both occasions with 3/4 users a user (not the same person) has had problems and their display froze. They log back in and the original display stays frozen in the room. On one ocasion he had further problems and he logged back in and created a third display! Yesterday it happened again and I had to reboot the server to loose the frozen display.
It seem the display is not being deleted when a user logs off.
As an interim measure, is there any way I can remove one frozen user on an active room?
What do I need to look at on the server to correct the fault?
Thanks

Which prosody version are you using?

peter@peternsomerset:~ sudo dpkg -l prosody [sudo] password for peter: 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.10.0-1build1 amd64 Lightweight Jabber/XMPP server peter@peternsomerset:~

I am not sure of the errors but I have read it should use a version 11.xx!
Assuming that is the case, can you please give details on how to install it from another repository? I was told not to do this but it may be necessary if repositories are not updated often.
As you are asking the question I assume prosody can cause display freezes!?

Thanks for your time
PS I am an enthusiastic amateur of quite an advanced age so please bear this in mind!

Peter H

Are you talking about freeze of the video, while watching someone’s video and it pauses for a minute and then continues? Or you were talking about someone is in the call, its connection goes bad or something and re-joins and you see two thumbnails for that participant one live and one from the old connection that never goes away? Which of those?

Apologies I did not make it clear,
The second one.
One user in the room had a bad connection and it disconnected but their display (using equal size display) just froze.
The user then entered the room again, their original display remained and another new connection was displayed. This also went bad and they logged back in. Their original 2 frozen displays remained and a third was created which did seem to work but on low bandwidth.
The same thing happened with another user the day after and the only way I could simplify the view for users was to reboot the server! The users also switched off their laptops but the frozen displays remained.
FWIW I held another meeting today and there was no bad connections and all was OK but I thing it is likely to happen again and it will put off novice users if it does.
Regards

Yes, we had reports for prosody 0.10 where the bosh timeout does not kick in to remove those stale participants and people reported back that prosody 0.11 fixes it. In a normal situation for no more than a minute that stale thumbnail will disappear.
To update add the debian repo from https://prosody.im/ and install it and do not forget to modify prosody config storage=none should become storage=memory.

Thanks very much for the info. Will look into updating before our next meeting.
Just for my limited intelligence could you tell me why the “config storage” does (or point me to the info).
Regards
Peter H

It is prosody had this none storage in older versions, which got changed in newer versions.

Ok thanks for your time.

Peter H

Hi,

I have been looking for the configuration file with “storage=null” before updating! but cannot find an entry!
Is this the file, if not can you please point to its location?
https://prosody.im/doc/example_config

Thanks

UPDATE

I have found this in /etc/prosody/conf.avail/<my_server>.cfg.lua.

– internal muc component
Component “internal.auth.cider123.duckdns.org” “muc”
storage = “none”
modules_enabled = {
“ping”;
}
admins = { “focus@auth.cider123.duckdns.org”, “jvb@auth.cider123.duckdns.org” }
muc_room_locking = false
muc_room_default_public_jids = true

I also have 3 other files in “conf.avail”:
example.com.cfg.lua, .cfg.lua.orig and localhost.cfg.lua.

Could you confirm all this is OK?

Thanks

Hi,
I decided to upgrade Prosody and it has created many problems:
Lost Moderator control to open a room
Keeps disconnecting and asks if I want to reconnect
Video and mic are muted but on “hovering over icon” I can see both are working, but clicking the icons do not toggle
Have lost the lower left icon to share screen
The ability to screen toggle with icon is missing and cannot find it in menus
There is a security option menu but I cannot insert a password
I had version 10 then altered the storage=“none” to “memory”
In sudo dpkg -l prosody it shows “0.11.6-1~bionic1” and the download/install went without errors.

Is there any way in reverting back to a working system with the old version as I need 2 rooms set for Monday or must rebuild the server!?

Thanks

Yes, you can install prosody 0.10 which should replace 0.11
Well, do you see errors in prosody logs, on restart of prosody service, what about when opening room?

Hi,
First of all I did not realise there were two “storage =” !
I had not changed “–internal muc” but it made no difference.
I keep getting disconnected because of a key problem but I have not altered anything:
Prosody.log (part):

Sep 11 22:00:52 startup info Shutting down: Received SIGTERM
Sep 11 22:00:52 general info Shutting down…
Sep 11 22:00:52 general info Shutdown status: Cleaning up
Sep 11 22:00:52 general info Shutdown complete
Sep 12 09:37:00 startup info Hello and welcome to Prosody version 0.11.6
Sep 12 09:37:00 startup info Prosody is using the select backend for connection handling
Sep 12 09:37:00 portmanager info Activated service ‘c2s’ on [::]:5222, [*]:5222
Sep 12 09:37:00 portmanager info Activated service ‘legacy_ssl’ on no ports
Sep 12 09:37:00 portmanager info Activated service ‘s2s’ on [::]:5269, [*]:5269
Sep 12 09:37:00 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Check that the permissions allow Prosody to read this file. (for localhost)
Sep 12 09:37:01 localhost:tls error Error creating context for c2s: error loading private key (Permission denied)
Sep 12 09:37:01 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
Sep 12 09:37:01 localhost:tls error Error creating contexts for s2sout: error loading private key (system lib)
Sep 12 09:37:01 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
Sep 12 09:37:01 localhost:tls error Error creating contexts for s2sin: error loading private key (system lib)
Sep 12 09:37:01 localhost:tls info Certificates loaded
Sep 12 09:37:08 c2s55fc4cfd8210 info Client connected
Sep 12 09:37:08 c2s55fc4cfd8210 info Client disconnected: connection closed
Sep 12 09:37:08 c2s55fc4cfe1c30 info Client connected
Sep 12 09:37:08 c2s55fc4cfe1c30 info Client disconnected: connection closed
Sep 12 09:37:13 c2s55fc4cfead60 info Client connected
Sep 12 09:37:13 c2s55fc4cfead60 info Client disconnected: connection closed
Sep 12 09:37:13 c2s55fc4cff40f0 info Client connected
Sep 12 09:37:13 c2s55fc4cff40f0 info Client disconnected: connection closed
Sep 12 09:37:13 c2s55fc4cffd820 info Client connected
Sep 12 09:37:13 c2s55fc4cffd820 info Client disconnected: connection closed
Sep 12 09:37:18 c2s55fc4d007700 info Client connected
Sep 12 09:37:18 c2s55fc4d007700 info Client disconnected: connection closed
Sep 12 09:37:18 c2s55fc4d010e30 info Client connected
Sep 12 09:37:18 c2s55fc4d010e30 info Client disconnected: connection closed
Sep 12 09:37:18 c2s55fc4d01a560 info Client connected
Sep 12 09:37:18 c2s55fc4d01a560 info Client disconnected: connection closed
Sep 12 09:37:22 c2s55fc4d024c10 info Client connected
Sep 12 09:37:22 c2s55fc4d024c10 info Client disconnected: connection closed
Sep 12 09:37:23 c2s55fc4d02f370 info Client connected
Sep 12 09:37:23 c2s55fc4d02f370 info Client disconnected: connection closed
Sep 12 09:37:23 c2s55fc4d0395c0 info Client connected
Sep 12 09:37:23 c2s55fc4d0395c0 info Client disconnected: connection closed
Sep 12 09:37:23 c2s55fc4d0437f0 info Client connected
Sep 12 09:37:23 c2s55fc4d0437f0 info Client disconnected: connection closed
Sep 12 09:37:28 c2s55fc4d04e010 info Client connected
Sep 12 09:37:28 c2s55fc4d04e010 info Client disconnected: connection closed
Sep 12 09:37:28 c2s55fc4d058240 info Client connected
Sep 12 09:37:28 c2s55fc4d058240 info Client disconnected: connection closed
Sep 12 09:37:28 c2s55fc4d062470 info Client connected
Sep 12 09:37:28 c2s55fc4d062470 info Client disconnected: connection closed
Sep 12 09:37:33 c2s55fc4d06cc90 info Client connected
Sep 12 09:37:33 c2s55fc4d06cc90 info Client disconnected: connection closed
Sep 12 09:37:33 c2s55fc4d076ec0 info Client connected
Sep 12 09:37:33 c2s55fc4d076ec0 info Client disconnected: connection closed
Sep 12 09:37:33 c2s55fc4d081d30 info Client connected

I did have a cert and it should last another 2 months from letsencrypt (if that is the problem), or would the upgrade have affected the key?

Regards
Peter H

What is the error in the js console ?

Can you bear with me, this is a little new!
Do you want the output from Chrome browser when trying to log into a room by doing a “ctrl+shift+J”?

If not please give details and I will post the O/P.

Thanks

Yep chrome javascript console

I think this is what you want!!?:

https://pastebin.com/5RNA9hKt

(still no display toggle or mic/camera activation)

Regards

Peter H

I get forbidden at the link, saying its private.

Apologies, should be OK now.