Prosody not working after upgrade to 0.11.5

Hello world.

this is really weird. I have installed Jitsi+jibri on 2 ubuntu servers with 18.04 and using jitsi stable repository. Everything was working, but for jibri to record in rooms with passwords, I have updated prosody to version 0.11.5 using prosody repositorys. After upgrade prosody from 0.10 to 0.11.5, prosody don’t work. First, I was getting this errors:

May 06 19:11:55 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Check that the permissions allow Prosody to read this file. (for localhost)
May 06 19:11:55 localhost:tls error Error creating context for c2s: error loading private key (Permission denied)
May 06 19:11:55 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
May 06 19:11:55 localhost:tls error Error creating contexts for s2sout: error loading private key (system lib)
May 06 19:11:55 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
May 06 19:11:55 localhost:tls error Error creating contexts for s2sin: error loading private key (system lib)

I fix it doing a chown prosody:prosody /etc/prosody/certs/* but now, I am getting this:

May 06 19:12:27 startup info Hello and welcome to Prosody version 0.11.5
May 06 19:12:27 startup info Prosody is using the select backend for connection handling
May 06 19:12:27 portmanager info Activated service ‘s2s’ on [::]:5269, []:5269
May 06 19:12:27 portmanager info Activated service ‘c2s’ on [::]:5222, [
]:5222
May 06 19:12:27 portmanager info Activated service ‘legacy_ssl’ on no ports
May 06 19:12:31 c2s55e442070f90 info Client connected
May 06 19:12:31 c2s55e442070f90 info Client disconnected: connection closed
May 06 19:12:36 c2s55e44207af10 info Client connected
May 06 19:12:36 c2s55e44207af10 info Client disconnected: connection closed
May 06 19:12:41 c2s55e4420841c0 info Client connected
May 06 19:12:41 c2s55e4420841c0 info Client disconnected: connection closed
May 06 19:12:44 c2s55e44208da60 info Client connected
May 06 19:12:44 c2s55e44208da60 info Client disconnected: connection closed
May 06 19:12:46 c2s55e442097200 info Client connected
May 06 19:12:46 c2s55e442097200 info Client disconnected: connection closed
May 06 19:12:51 c2s55e4420a0f00 info Client connected
May 06 19:12:51 c2s55e4420a0f00 info Client disconnected: connection closed

I tryed to change at my /etc/prosody/conf.avail/my.jitsy.syte.lua the lines

storage = ‘none’

to

storage = ‘memory’

As I see on this post but with no luck.

Any help would be apreciated.

Thank you

Try adding these https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet-prosody/prosody.cfg.lua-jvb.example#L14
https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet-prosody/prosody.cfg.lua-jvb.example#L15

Hi damencho,

I already got those lines at /etc/prosody/config.avail/my.jitsy.site.lua

I must add them at another file?

thank you

I am also getting this errors in jicofo.log:

stream:errorThis server does not serve auth.my.jitsi.site</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1059)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)
Jicofo 2020-05-06 20:55:32.272 ADVERTENCIA: [29] org.jivesoftware.smack.AbstractXMPPConnection.callConnectionClosedOnErrorListener() Connection XMPPTCPConnection[not-authenticated] (0) closed with error
org.jivesoftware.smack.XMPPException$StreamErrorException: host-unknown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
stream:errorThis server does not serve auth.my.jitsi.site</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1064)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)

and

Jicofo 2020-05-06 20:55:32.863 GRAVE: [46] org.jitsi.meet.ComponentMain.log() java.net.ConnectException: Conexión rehusada (Connection refused), host:localhost, port:5347
org.xmpp.component.ComponentException: java.net.ConnectException: Conexión rehusada (Connection refused)
at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:296)
at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:242)
at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:222)
at org.jitsi.meet.ComponentMain.lambda$getConnectCallable$0(ComponentMain.java:285)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Conexión rehusada (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:174)
… 11 more

Prosody not running or something blocking access of jicofo to it, or not listening on that port …

Does your /etc/prosody/prosody.cfg.lua contain an include statement to actually load your /etc/prosody/config.avail/my.jitsy.site.lua? This could look like Include "config.avail/*.cfg.lua". Make sure the include statement matches your actual file paths, as I think in the default config this would likely be config.d/*.cfg.lua rather than config.avail/.

Well, I am a coward and I uninstall and reinstall all, but using jitsi’s repos prosody in version 0.10, and now all is working again.

I will try doing it next week, I need the server working for tomorrow and I prefer not having the choice of recording but a working meeting server.

As I say, next week I will try to upgrade again and try your workaround PLOTKA, thank you.

But now, i got 3 errors in jicofo. Nothing really serious, It seems all is working, except users focus when they are talking to see them in the big picture. This are the errors:

Jicofo 2020-05-07 10:09:10.762 GRAVE: [27] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.getFeatures().144 Failed to discover features for focus.my.jitsi.site: XMPP error reply received from focus.my.jitsi.site: XMPPError: service-unavailable - wait
Jicofo 2020-05-07 10:09:10.773 GRAVE: [27] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.getFeatures().144 Failed to discover features for conferenceduration.my.jitsi.site: XMPP error reply received from conferenceduration.my.jitsi.site: XMPPError: service-unavailable - cancel
Jicofo 2020-05-07 10:09:10.775 GRAVE: [27] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.getFeatures().144 Failed to discover features for speakerstats.my.jitsi.site: XMPP error reply received from speakerstats.my.jitsi.site: XMPPError: service-unavailable - cancel

Thank you for your help, I really appreciate it

P.D. I forgot to mention that this errors happens only on Jicofo startup.

I believe this is normal if jicofo happens to be up and running before prosody is up. I would not worry about these errors if the only occur shortly after starting the services.

Thanks a lot plokta, I really really appreciate your help, my skills are low and I am lost in this jitsi / java world!!

P.D. It seems that all is working fine. Focus, statistics… Thanks again

I’ve done many of the changes that have been listed, from change storage=“memory”, to adjusting permission on the /cert directory. Nothing was working as I would continually get the blank screen in the meeting room and then a disconnect.

Finally I took a stab at the Include “conf.d/*.cfg.lua” entry as that was missing from my test server, but my dev server still had Prosody 10 running on it with that entry. It worked immediately after restarting prosody, jicofo, jitsi-videobridge2.

Actually it’s a bit confusing with both a conf.avail and a conf.d directory. The conf.d simply has a link that points to conf.avail anyway. So I changed the prosody.cfg.lua to have the Include “conf.avail/*.cfg.lua” and that works as well. Either way, just make sure that statement is included.

Thanks @plokta