Jitsi Keeps Disconnecting in 30 Seconds

Hi,
I am getting the above and my mic and camera are muted (and cannot switch them on) but this is after another problem listed 21 days ago “Multiple Frozen Displays”.

I had an install of Ubuntu 18.04 and used their repository to instal prosody which was old and I installed version 11.* but did not at first change the “storage=memory” in config. Afterwards I could not get Jitis to function. I then gave up and was going to rebuild but as Ubuntu 20.04 LTS had been released I decided to tried to upgrade. The upgrade went OK and I checked prosody was still version 11 and had the changes to storage.

What is the most likely cause of the above and where do I start looking to resolve it?
A reference to any other information would be appreciated
I assume if I cannot sort this out would “apt uninstall” remove it or do I need other commands to completely remove all jitsi files?

Thanks

Check the JS console for the error. That should tell where to look next.

OK thanks

Hi,
There are repeating errors, I filtered the info with errors tab, I think there may be something basic missing or corrupted:

/http-bind?room=test:1 Failed to load resource: the server responded with a status of 502 ()
Logger.js:154 2020-09-30T18:41:51.574Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: null Script: null Line: null Column: null StackTrace: Error: Strophe: request id 1.1 error 502 happened
at Object.r.Strophe.log (strophe.util.js:89)
at Object.error (strophe.umd.js:1392)
at D.Bosh._onRequestStateChange (strophe.umd.js:5017)
o @ Logger.js:154
Logger.js:154 2020-09-30T18:41:51.575Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: request id 1.1 error 502 happened
o @ Logger.js:154
/http-bind?room=test:1 Failed to load resource: the server responded with a status of 502 ()
Logger.js:154 2020-09-30T18:41:51.640Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: null Script: null Line: null Column: null StackTrace: Error: Strophe: request id 2.2 error 502 happened
at Object.r.Strophe.log (strophe.util.js:89)
at Object.error (strophe.umd.js:1392)
at D.Bosh._onRequestStateChange (strophe.umd.js:5017)
o @ Logger.js:154
Logger.js:154 2020-09-30T18:41:51.641Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: request id 2.2 error 502 happened
o @ Logger.js:154
/http-bind?room=test:1 Failed to load resource: the server responded with a status of 502 ()
Logger.js:154 2020-09-30T18:41:59.656Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: null Script: null Line: null Column: null StackTrace: Error: Strophe: request id 3.3 error 502 happened
at Object.r.Strophe.log (strophe.util.js:89)
at Object.error (strophe.umd.js:1392)
at D.Bosh._onRequestStateChange (strophe.umd.js:5017)
o @ Logger.js:154
Logger.js:154 2020-09-30T18:41:59.657Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: request id 3.3 error 502 happened
o @ Logger.js:154

I am very new to java console but hope this gives a clue!?

I cannot see any references to prosody or jicofo so I assume its a basic problem.
I can get to my server so at least something still works!

Thanks

This indicates there is an error in prosody, so check prosody logs.

I assume I don’t have any key(s)!?
I did have them before my problems in updating prosody to version 11 so I maybe they got deleted on the Ubuntu server upgrade.
Is there a way to generate/reproduce keys or would it be very complicated if I still have old remnants!
A pointer to any information would be helpful.

Thanks

This is the o/p from prosody log1:

peter@peternsomerset:/var/log/prosody$ cat prosody.err.1
May 02 19:02:19 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 02 19:02:19 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 02 19:33:05 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 02 19:33:05 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 03 00:25:34 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Thanks