Dear Jitsi Team,
I keep getting errors and was able to track them down to this specific circumstance. It is all about the authentication, where I want to lock jtisi so only me as a moderator can start and host meetings, else the user authentication prompt will just appear.
I am running jitsi on my private server with all necessary ports opened. I can reinstall jitsi meet and redo the entire process and it will work for a couple of days, but then suddenly I am coming back to the same point.
The error I get is shown here in the console is as shown in the image.
The jvb log shows:
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$9(MucClient.java:635)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
JVB 2023-03-15 21:24:30.680 WARNING: [32] [hostname=localhost id=shard] MucClient.setPresenceExtensions#467: Cannot set presence extension: not connected.
and the jicofo.log
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
at org.jitsi.jicofo.xmpp.XmppProvider.doConnect(XmppProvider.kt:165)
at org.jitsi.jicofo.xmpp.XmppProvider.start$lambda-1(XmppProvider.kt:125)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
finally prosody
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
at org.jitsi.jicofo.xmpp.XmppProvider.doConnect(XmppProvider.kt:165)
at org.jitsi.jicofo.xmpp.XmppProvider.start$lambda-1(XmppProvider.kt:125)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
-bash: /var/log/prosody/prosody.log: Permission denied
Now I undo authentication and runs perfectly again, when I reinstall jitsi meet and redo authentication according to Self-Hosting Guide - Debian/Ubuntu server | Jitsi Meet - Access Control it works for a couple of days.
I have double checked but I cannot find the reason behind and therefor your help is greatly appreciated.
Update:
when I just changed the Authentication from internal plain to internal hashed it started to work again, any user is prompted for user and password. Now its working, question is for how long - and is this error known or am I doing something terribly wrong ?