Starting with 9909 recording/transcription fails

[bmagistro]

Possibly related to #2008 + #1966

Logs below are from jibri on 9909 but the same issue occurs on 9955. no configuration changes other than a sync of the compose file were made. In there is the XMPP_RECORDER_DOMAIN set to recorder.meet.jitsi but nothing aliases that. A snippet from transcription log on console -- didn't save before getting things working is also included. It was this message combined with the the XMPP_RECORDER_DOMAIN change that tipped me off to this setting in the env. Dropping that from the env file gets things back to working. The advanced documentation https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#advanced-configuration shows this being set as previously mentioned. This may just be a point of documentation clarification around if/when this needs to be set or it may be a case of an alias is missing on a container.

I have this up in a test environment to validate the upgrade for us so can switch settings and grab logs pretty easily.

jibri.log

transcription

2025-02-02 22:59:09.515 INFO: [37] TranscriptionGateway.getCustomTranscriptionServiceClass#173: [ctx=17385371495121549458194] Transcriber class retrieved from config: org.jitsi.jigasi.transcription.VoskTranscriptionService
2025-02-02 22:59:09.516 INFO: [37] JvbConference.start#589: [ctx=17385371495121549458194] Starting JVB conference room: [email protected]
2025-02-02 22:59:09.536 INFO: [37] JvbConference.setXmppProvider#734: [ctx=17385371495121549458194] Using ProtocolProviderServiceJabberImpl(Jabber:[email protected]/6f75a416)
2025-02-02 22:59:09.570 SEVERE: [222] net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin: Failed to connect to XMPP service for:ProtocolProviderServiceJabberImpl(Jabber:[email protected]/6f75a416)
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:error><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>This server does not serve recorder.meet.jitsi</text></stream:error>
	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:984)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
	at java.base/java.lang.Thread.run(Thread.java:840)
2025-02-02 22:59:09.571 SEVERE: [57] JvbConference.registrationStateChangedInternal#799: [ctx=17385371495121549458194] XMPP Connection failed. RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=6; reason=host-unknown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions

[saghul]

Logs below are from jibri on 9909 but the same issue occurs on 9955. no configuration changes other than a sync of the compose file were made. In there is the XMPP_RECORDER_DOMAIN set to recorder.meet.jitsi but nothing aliases that.

If you synced the compose file, that variable is set nothing, also not in .env. It's just there for backwards compatibility for those who set it in the past.

Can you share your .env file?

The advanced documentation https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#advanced-configuration shows this being set as previously mentioned. This may just be a point of documentation clarification around if/when this needs to be set or it may be a case of an alias is missing on a container.

I'll get that updated.

[bmagistro]

Attached here. We had the XMPP_RECORDER_DOMAIN set but I don't remember why we set it in the first place. Possibly copying from the docs when trying to get recording configured the first time and then left alone once things were working. In general we try to keep the compose and env as close to what is in git as we can to reduce variables/troubleshooting.

I've also attached the diff from the sync associated with this update (prev was 9823). Looking at this when I'm a little more awake, that parameter probably wouldn't have done anything before as it wasnt included as a var in the compose file so with the recent sync + update it highlighted a misconfig on our part is my guess.

config.env.txt
sync.diff.txt