Changing BOSH URL breaks recording

[ktechmidas]

Changed the bosh URL to the FQDN as suggested right here: #183 to fix mobile clients being unable to connect

Just tried changing the BOSH URL back to a relative value (ie /http-bind) and now recording works again and iOS is broken....

Using latest iOS btw: 20.2.3

[saghul]

How does your BOSH URL look like now? Why do you think that’s the cause? What kind of TLS certificate do you have?

[ktechmidas]

We have a letsencrypt certificate, the digicert checker tells us we have everything (including intermediates) installed correctly.

I think it's the cause because when we set the BOSH URL to 'https://meet.domain.com/http-bind' iOS works fine but recording breaks.... when we set it to '/http-bind' iOS breaks but recording works. This is repeatable 100% on this side....

[ktechmidas]

I think in order to test this you can set the BOSH URL to the FQDN in config.js on the latest docker release and if I'm right recording will break on your side as well

[ktechmidas]

Sorry for the multipost... just gonna provide some logs as well, with BOSH_URL as absolute domain:

jibri_1    | 2020-06-08 07:41:33.185 FINE: [60] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://meet.jitsi/test#config.iAmR
ecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME="Jibri"&config.an
alytics.disabled=true&config.p2p.enabled=false                                                                                                        
jibri_1    | 2020-06-08 07:42:04.027 SEVERE: [60] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Timed out waiting for call page to load       
jibri_1    | 2020-06-08 07:42:04.030 INFO: [60] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Starting up to
 Error: SESSION Failed to join call                                                                                                                   
jibri_1    | 2020-06-08 07:42:04.031 INFO: [60] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service t
ransitioning from state Starting up to Error: SESSION Failed to join call                                                                             
jibri_1    | 2020-06-08 07:42:04.032 INFO: [60] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error, sending error iq <iq to='jibri
brewery@internal-muc.meet.jitsi/focus' id='60jZ2-27' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error'/></
iq>                                                                                                                                                   
jibri_1    | 2020-06-08 07:42:04.032 FINE: [60] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recordin
g                                                                                                                                                     
jibri_1    | 2020-06-08 07:42:04.033 INFO: [60] org.jitsi.jibri.JibriManager.stopService() Stopping the current service                               
jibri_1    | 2020-06-08 07:42:04.033 INFO: [60] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer                       
jibri_1    | 2020-06-08 07:42:04.034 INFO: [60] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process                            
jibri_1    | 2020-06-08 07:42:04.034 INFO: [60] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value null                      
jibri_1    | 2020-06-08 07:42:04.034 INFO: [60] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium

[ktechmidas]

just tested again, works with the non-absolute domain set as bosh so it's definitely the bosh that's failing here....

Is it possible to set config.bosh in the url jibri uses to access jitsi easily? Without recompiling the JAR?

[Neustradamus]

@saghul, @ktechmidas needs a reply...

[ktechmidas]

Hey there's someone on the old thread with the same issue... can we fix this now?

#240 (comment)

[saghul]

We reverted the change to the BOSH URL.