Jigasi doesn't work - certificates

I am running docker-jitsi-meet with the jigasi extension on a Synology. Everything works, but Jigasi. I can see the ±sign and type in a number, but no call is made, instead an error message appears.

I can’t use Let’s Encrypt on the Synology in the container, because everything has to be forwarded by a nginx proxy, which causes the let’s encrypt certificate creation to fail. The proxy itself knows already the certificate and encrypts on the frontend. I proxy this traffic back to the probably selfsigned jitsi-port 8443 in docker.

When I read the docker logs for jigasi, I found 4 error messages:

Jigasi 2019-04-05 23:26:50.081 WARNING: [11] impl.sysactivity.SystemActivityNotifications.<clinit>().140 Failed to initialize native counterpart
java.lang.UnsatisfiedLinkError: /tmp/jna--1160142225/jna1613311725153485067.tmp: libgdk-x11-2.0.so.0: cannot open shared object file: No such file or directory
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824)
	at java.lang.Runtime.load0(Runtime.java:809)
	at java.lang.System.load(System.java:1086)
	at org.jitsi.util.JNIUtils.loadLibrary(JNIUtils.java:96)
	at org.jitsi.util.JNIUtils.loadLibrary(JNIUtils.java:37)
	at net.java.sip.communicator.impl.sysactivity.SystemActivityNotifications.<clinit>(SystemActivityNotifications.java:124)
	at net.java.sip.communicator.impl.sysactivity.SystemActivityNotificationsServiceImpl.isSupported(SystemActivityNotificationsServiceImpl.java:606)
	at net.java.sip.communicator.impl.sysactivity.SystemActivityNotificationsServiceImpl.start(SystemActivityNotificationsServiceImpl.java:143)
	at net.java.sip.communicator.impl.sysactivity.SysActivityActivator.start(SysActivityActivator.java:70)
	at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:307)
	at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:472)
	at org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:137)
	at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:122)
	at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:28)
	at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:231)



Jigasi 2019-04-05 23:26:50.210 SEVERE: [11] impl.sysactivity.NetworkManagerListenerImpl.<init>().60 Cannot obtain dbus connection
org.freedesktop.dbus.exceptions.DBusException: Failed to connect to bus No such file or directory
	at org.freedesktop.dbus.DBusConnection.<init>(Unknown Source)
	at org.freedesktop.dbus.DBusConnection.getConnection(Unknown Source)
	at net.java.sip.communicator.impl.sysactivity.NetworkManagerListenerImpl.<init>(NetworkManagerListenerImpl.java:56)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.lang.Class.newInstance(Class.java:442)
	at net.java.sip.communicator.impl.sysactivity.SystemActivityNotificationsServiceImpl.getCurrentRunningManager(SystemActivityNotificationsServiceImpl.java:643)
	at net.java.sip.communicator.impl.sysactivity.SystemActivityNotificationsServiceImpl.start(SystemActivityNotificationsServiceImpl.java:154)
	at net.java.sip.communicator.impl.sysactivity.SysActivityActivator.start(SysActivityActivator.java:70)
	at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:307)
	at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:472)
	at org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:137)
	at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:122)
	at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:28)
	at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:231)



Jigasi 2019-04-05 23:26:51.252 SEVERE: [11] org.jitsi.impl.neomedia.device.DeviceConfiguration.log() Failed to register custom Renderer org.jitsi.impl.neomedia.jmfext.media.renderer.audio.PulseAudioRenderer with JMF.
java.lang.IllegalStateException: audioSystem
	at org.jitsi.impl.neomedia.jmfext.media.renderer.audio.PulseAudioRenderer.<init>(PulseAudioRenderer.java:155)
	at org.jitsi.impl.neomedia.jmfext.media.renderer.audio.PulseAudioRenderer.<init>(PulseAudioRenderer.java:135)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.lang.Class.newInstance(Class.java:442)
	at org.jitsi.impl.neomedia.device.DeviceConfiguration.registerCustomRenderers(DeviceConfiguration.java:1045)
	at org.jitsi.impl.neomedia.device.DeviceConfiguration.<init>(DeviceConfiguration.java:364)
	at org.jitsi.impl.neomedia.MediaServiceImpl.<init>(MediaServiceImpl.java:160)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.lang.Class.newInstance(Class.java:442)
	at org.jitsi.impl.libjitsi.LibJitsiImpl$ServiceLock.initializeService(LibJitsiImpl.java:196)
	at org.jitsi.impl.libjitsi.LibJitsiImpl$ServiceLock.getService(LibJitsiImpl.java:131)
	at org.jitsi.impl.libjitsi.LibJitsiImpl.getService(LibJitsiImpl.java:91)
	at org.jitsi.impl.libjitsi.LibJitsiOSGiImpl.getService(LibJitsiOSGiImpl.java:95)
	at org.jitsi.service.libjitsi.LibJitsi.invokeGetServiceOnImpl(LibJitsi.java:172)
	at org.jitsi.service.libjitsi.LibJitsi.getMediaService(LibJitsi.java:124)
	at net.java.sip.communicator.impl.neomedia.NeomediaActivator.start(NeomediaActivator.java:391)
	at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:307)
	at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:472)
	at org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:137)
	at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:122)
	at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:28)
	at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:231)



Jigasi 2019-04-05 23:27:58.356 SEVERE: [43] impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin().1004 Failed to connect to XMPP service
org.jivesoftware.smack.SmackException$SecurityRequiredByClientException: SSL/TLS required by client but not supported by server
	at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:390)
	at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1301)
	at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:971)
	at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:796)
	at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:501)
	at org.jitsi.jigasi.util.RegisterThread.run(RegisterThread.java:59)
Jigasi 2019-04-05 23:57:58.197 WARNING: [54] org.jivesoftware.smackx.ping.PingManager.pingServerIfNecessary() XMPPConnection was not authenticated[cont-finish.d] executing container finish scripts...
 

I followed the last one and looked into the logs of prosody:

[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-set-timezone: executing... 
[cont-init.d] 01-set-timezone: exited 0.
[cont-init.d] 10-config: executing... 
The directory /config/data is not owned by the current user, won't be able to write files to it
The directory /config/data is not owned by the current user, won't be able to write files to it
[cont-init.d] 10-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
startup             info	Hello and welcome to Prosody version 0.11.2
startup             info	Prosody is using the select backend for connection handling
portmanager         info	Activated service 'component' on [*]:5347
certmanager         error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for focus.meet.jitsi)
focus.meet.jitsi:tls  error	Error creating context for c2s: error loading private key (No such file or directory)
mv: cannot stat '/config/data/*.crt': No such file or directory
mv: cannot stat '/config/data/*.key': No such file or directory
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Previous error (see logs), or other system error. (for focus.meet.jitsi)
focus.meet.jitsi:tls  error	Error creating contexts for s2sout: error loading private key (system lib)
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Previous error (see logs), or other system error. (for focus.meet.jitsi)
focus.meet.jitsi:tls  error	Error creating contexts for s2sin: error loading private key (system lib)
portmanager           info	Activated service 's2s' on [*]:5269, [::]:5269
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for muc.meet.jitsi)
muc.meet.jitsi:tls    error	Error creating context for c2s: error loading private key (No such file or directory)
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Previous error (see logs), or other system error. (for muc.meet.jitsi)
muc.meet.jitsi:tls    error	Error creating contexts for s2sout: error loading private key (system lib)
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Previous error (see logs), or other system error. (for muc.meet.jitsi)
muc.meet.jitsi:tls    error	Error creating contexts for s2sin: error loading private key (system lib)
portmanager           info	Activated service 'c2s' on [*]:5222, [::]:5222
portmanager           info	Activated service 'legacy_ssl' on no ports
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for guest.meet.jitsi)
guest.meet.jitsi:tls  error	Error creating context for c2s: error loading private key (No such file or directory)
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for guest.meet.jitsi)
guest.meet.jitsi:tls  error	Error creating contexts for s2sout: error loading private key (No such file or directory)
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for guest.meet.jitsi)
guest.meet.jitsi:tls  error	Error creating contexts for s2sin: error loading private key (No such file or directory)
certmanager           error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for internal-muc.meet.jitsi)
internal-muc.meet.jitsi:tls  error	Error creating context for c2s: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for internal-muc.meet.jitsi)
internal-muc.meet.jitsi:tls  error	Error creating contexts for s2sout: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for internal-muc.meet.jitsi)
internal-muc.meet.jitsi:tls  error	Error creating contexts for s2sin: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/auth.meet.jitsi.key': Check that the path is correct, and the file exists. (for auth.meet.jitsi)
auth.meet.jitsi:tls          error	Error creating context for c2s: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/auth.meet.jitsi.key': Check that the path is correct, and the file exists. (for auth.meet.jitsi)
auth.meet.jitsi:tls          error	Error creating contexts for s2sout: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/auth.meet.jitsi.key': Check that the path is correct, and the file exists. (for auth.meet.jitsi)
auth.meet.jitsi:tls          error	Error creating contexts for s2sin: error loading private key (No such file or directory)
portmanager                  info	Activated service 'http' on [*]:5280, [::]:5280
portmanager                  info	Activated service 'https' on no ports
certmanager                  error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for meet.jitsi)
meet.jitsi:tls               error	Error creating context for c2s: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for meet.jitsi)
meet.jitsi:tls               error	Error creating contexts for s2sout: error loading private key (No such file or directory)
certmanager                  error	SSL/TLS: Failed to load '/config/certs/meet.jitsi.key': Check that the path is correct, and the file exists. (for meet.jitsi)
meet.jitsi:tls               error	Error creating contexts for s2sin: error loading private key (No such file or directory)
c2s7f57564cd1b0              info	Client connected
jcp7f57564d3f30              info	Incoming Jabber component connection
focus.meet.jitsi:component   info	External component successfully authenticated
c2s7f57564cd1b0              info	Authenticated as [e-mail]
c2s7f57565561f0              info	Client connected
c2s7f57565561f0              info	Authenticated as [e-mail]
c2s7f57565d8d10              info	Client connected
c2s7f57565d8d10              info	Client disconnected: connection closed
mod_bosh                     info	New BOSH session, assigned it sid 'b9af57ac-43bc-40b4-a5a4-ba4fb642c375'
boshb9af57ac-43bc-40b4-a5a4-ba4fb642c375  info	Authenticated as [e-mail]
mod_bosh                                  info	New BOSH session, assigned it sid 'e426d549-fb68-4d43-a63b-1706a09692c5'
boshe426d549-fb68-4d43-a63b-1706a09692c5  info	Authenticated as [e-mail]
boshe426d549-fb68-4d43-a63b-1706a09692c5  info	BOSH client disconnected: session close
boshb9af57ac-43bc-40b4-a5a4-ba4fb642c375  info	BOSH client disconnected: session close

Some help would be greatly appreciated.

[rahimnathwani]

@saschafoerster

It looks your issue was the same as mine. If you were trying to run the dev branch by just running docker-compose ... up -d as mentioned by @netaskd then the .yml files were probably just pulling from docker hub. To solve it, you should either build the images using make as suggested by @saghul or do what I did.

[saghul]

• Added XMPP_SERVER=xmpp.meet.jitsi to .env

• Added XMPP_BOSH_URL_BASE=http://xmpp.meet.jitsi:5280 to .env

Those values are already there: https://github.com/jitsi/docker-jitsi-meet/blob/dev/env.example#L140 are you suere you checked the right branch?

• In docker-compose.xml, replaced 4 instances of image: jitsi/ with build: so that images would be built from local config, and the right files would be copied using the COPY directive in the relevant DockerFile

• In jigasi.xml, replaced image: jitsi/ with build:

You don’t need to do this. You can build the images locally by just running make at the toplevel.

* Entered the prosody container's shell with `docker-compose exec prosody /bin/bash` and ran `prosodyctl --config /config/prosody.cfg.lua register <username> meet.jitsi <password>`

You shouldn’t need to do this. Have you uncommented these options? https://github.com/jitsi/docker-jitsi-meet/blob/dev/env.example#L199