Jibri cannot connect to Jitsi

[Muhannad_Darnasser]

I have installed jitsi on a Ubuntu 20 server and it is running fine, and also I installed Jibri on a different Ubuntu 20 server following this post instructions:

How-to to setup integrated Jitsi and Jibri for dummies, my comprehensive tutorial for the beginner

Troubleshooting steps - Jitsi and Jibri. So now we have a server for Jitsi Meet and possibly also anotherone with Jibri and we expect to start videoconferences, recordings and youtube-streams… OR AT LEAST WE THINK WE HAVE! If things go awry, then the search is on! It is one thing to try the black box and if it doesn’t work (or part of it doesn’t) start searching the community forum or your favorite search engine. It is more helpful to find more specific information from the logfiles that are g…

but each time I tried to start recording in a jitsi meet, I face the issue that says “Recording unavailable”
I listed the log file from Jibri:

org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [jitsi.valitracks.io:5222] (jitsi.valitracks.io/51.15.226.145:5222)' failed because: java.net.ConnectException: Connection refused (Connection refused)
        at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:664)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:849)
        at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
        at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:625)
        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)

Also I tried to telnet from Jibri server to jitsi server on port 5222 and it can connect to the server

telnet jitsi.valitracks.io 5222
Trying 51.15.226.145...
Connected to jitsi.valitracks.io.
Escape character is '^]'.

this is the java version I am using with Jibri

openjdk version "1.8.0_292"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)

Can any one please help where to debug the issue?

[saghul]

Please use java 11, any lower version is no longer supported.

[Muhannad_Darnasser]

the java error is gone, thanks for the help, but now I am facing this issue, I will try to debug it more, but if you can please point me to the error that I am making, I appreciate it, this is the log

2022-08-09 12:55:05.299 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2022-08-09 12:55:05.534 INFO: [1] MainKt.setupLegacyConfig#211: Checking legacy config file /etc/jitsi/jibri/config.json
2022-08-09 12:55:06.500 INFO: [1] JibriConfigKt.loadConfigFromFile#190: Parsed legacy config:
JibriConfig(jibriId=null, recordingDirectory=/srv/recordings, singleUseMode=null, enabledStatsD=null, finalizeRecordingScriptPath=, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[jitsi.valitracks.io], xmppDomain=jitsi.valitracks.io, baseUrl=null, controlLogin=XmppCredentials(domain=auth.jitsi.valitracks.io, port=null, username=jibri, password=*****), controlMuc=XmppMuc(domain=internal.auth.jitsi.valitracks.io, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.jitsi.valitracks.io, port=null, username=recorder, password=*****), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true, securityMode=null)])
2022-08-09 12:55:06.533 INFO: [1] MainKt.main#55: Jibri starting up with id
2022-08-09 12:55:07.133 INFO: [1] JwtInfo$Companion.fromConfig#154: got jwtConfig: {}

2022-08-09 12:55:07.134 INFO: [1] JwtInfo$Companion.fromConfig#164: Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/opt/jitsi/jibri/jibri.jar!/reference.conf: 62: No configuration setting found for key 'signing-key-path'
2022-08-09 12:55:07.163 INFO: [1] MainKt.main#125: Using port 3333 for internal HTTP API
2022-08-09 12:55:07.199 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-08-09 12:55:07.813 INFO: [1] XmppApi.updatePresence#203: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2022-08-09 12:55:07.826 INFO: [1] XmppApi.start#156: Connecting to xmpp environment on jitsi.valitracks.io with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[jitsi.valitracks.io], xmppDomain=jitsi.valitracks.io, baseUrl=null, controlLogin=XmppCredentials(domain=auth.jitsi.valitracks.io, port=null, username=jibri, password=*****), controlMuc=XmppMuc(domain=internal.auth.jitsi.valitracks.io, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.jitsi.valitracks.io, port=null, username=recorder, password=*****), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true, securityMode=null)
2022-08-09 12:55:07.827 INFO: [1] XmppApi.start#168: The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2022-08-09 12:55:07.859 INFO: [29] [hostname=jitsi.valitracks.io id=jitsi.valitracks.io] MucClient.initializeConnectAndJoin#278: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=jitsi.valitracks.io domain=auth.jitsi.valitracks.io hostname=jitsi.valitracks.io port=null username=jibri mucs=[jibribrewery@internal.auth.jitsi.valitracks.io] mucNickname=jibri-nickname disableCertificateVerification=true]
2022-08-09 12:55:07.861 INFO: [1] MainKt.main#152: Using port 2222 for HTTP API
2022-08-09 12:55:07.898 WARNING: [29] MucClient.createXMPPTCPConnectionConfiguration#116: Disabling certificate verification!
2022-08-09 12:55:07.939 INFO: [29] [hostname=jitsi.valitracks.io id=jitsi.valitracks.io] MucClient.initializeConnectAndJoin#340: Dispatching a thread to connect and login.
2022-08-09 12:55:08.187 FINE: [29] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: xmpp-connected:xmpp_server_host:jitsi.valitracks.io
2022-08-09 12:55:08.188 INFO: [29] [hostname=jitsi.valitracks.io id=jitsi.valitracks.io] MucClient$2.connected#311: Connected.
2022-08-09 12:55:08.188 INFO: [29] [hostname=jitsi.valitracks.io id=jitsi.valitracks.io] MucClient.lambda$getConnectAndLoginCallable$7#636: Logging in.
2022-08-09 12:55:08.287 INFO: [29] [hostname=jitsi.valitracks.io id=jitsi.valitracks.io] MucClient$2.authenticated#317: Authenticated, b=false
2022-08-09 12:55:08.385 INFO: [29] [hostname=jitsi.valitracks.io id=jitsi.valitracks.io] MucClient$MucWrapper.join#760: Joined MUC: jibribrewery@internal.auth.jitsi.valitracks.io

Thanks

[Freddie]

Share the complete log. Also, share your jibri.conf.
By the way, the guide you used is outdated.

[Muhannad_Darnasser]

it is the full log for Jibri, I restarted Jibri and tried a call to have a fresh and simple log file.
This is my Jibri.config

jibri {
api {
        xmpp {
            environments = [
                {
                    name = "jitsi.valitracks.io"
                    xmpp-server-hosts = ["jitsi.valitracks.io"],
                    xmpp-domain = "jitsi.valitracks.io"
                    control-login {
                        domain = "auth.jitsi.valitracks.io"
                        username = "jibri"
                        password = "************"
                        port = 5222
                    }
                    control-muc {
                        domain = "internal.auth.jitsi.valitracks.io"
                        room-name = "JibriBrewery"
                        nickname = "myjibri-1-2-3-4"
                    }
                    call-login {
                        domain = "recorder.jitsi.valitracks.io"
                        username = "recorder"
                        password = "***************"
                    }
                    strip-from-room-domain = "conference."
                    trust-all-xmpp-certs = true
                    usage-timeout = 0
                }
            ]
        }
    }
}

Also do I need to register Auth.jitsi and internal.auth to my DNS as A records ?

[Freddie]

Again, if you used that tutorial as a guide, it’s outdated. You likely configured config.json, which has been deprecated. Jibri’s configuration is now stored in jibri.conf. I’d recommend checking this tutorial for guidance:

TUTORIAL - How to Install the NEW JIBRI

If you’re here, you likely already know what Jibri is and you are looking to deploy it in your own environment (or upgrade your already installed instance to the latest version). You WILL need to install this latest version of Jibri or upgrade to this latest version (if you already deployed Jibri) as there will no longer be support for the previous version soon. To make this as concise as possible, I won’t go into the architecture and all the features of Jibri. You can check out my other Tutori…

And no, you do not need to register those domains as A records, they’re used internally by Prosody.

[Muhannad_Darnasser]

@Freddie @saghul Thank you very much, yes @Freddie it was the outdated issue, but I just forgot to restart the servers after I moved to the new config. so it is working fine now.