Failed to start Jibri Process

I get this message after installing jibri on a stand-alone server

Checkout jibri logs or the journal logs for that service on the machine. What errors do you see there?

this is the log

2022-09-14 07:28:14.297 WARNING: [32] [hostname=1.2.3.4 id=1.2.3.4] MucClient.lambda$getConnectAndLoginCallable$9#631: Error connecting:
org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [/1.2.3.4:5222] (/1.2.3.4:5222)' failed because: java.net.SocketTimeoutException: connect timed out
        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$9(MucClient.java:626)
        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)
2022-09-14 07:28:15.196 INFO: [45] InternalHttpApi$internalApiModule$2$1$1.invokeSuspend#58: Jibri gracefully shutting down
2022-09-14 07:28:15.213 INFO: [47] MainKt$main$gracefulShutdownHandler$1.invoke#111: Jibri has been told to graceful shutdown, waiting to be idle before exiting

i don`t know from where get the ip 1.2.3.4 this is my configue file for jibri

jibri {
   // A unique identifier for this Jibri
   // TODO: eventually this will be required with no default
   id = ""
   // Whether or not Jibri should return to idle state after handling
   // (successfully or unsuccessfully) a request. A value of ‘true’
   // here means that a Jibri will NOT return back to the IDLE state
   // and will need to be restarted in order to be used again.
   single-use-mode = false
   api {
      http {
      external-api-port = 2222
      internal-api-port = 3333
      }
      xmpp {
      // See example_xmpp_envs.conf for an example of what is expected here
      environments = [
         {
            name = "prod environment"
            xmpp-server-hosts = ["meet.elemental-tech.com"]
            xmpp-domain = "meet.elemental-tech.com"


            control-muc {
               domain = "internal.auth.meet.elemental-tech.com"
               room-name = "JibriBrewery"
               nickname = "jibri-nickname"
            }

            control-login {
               domain = "auth.meet.elemental-tech.com"
               username = "jibri"
               password = "JPwd"
            }

            call-login {
               domain = "recorder.meet.elemental-tech.com"
               username = "recorder"
               password = "RPwd"
            }

            strip-from-room-domain = "conference."
            usage-timeout = 0
            trust-all-xmpp-certs = true
         }
      ]
      }
   }
   recording {
      recordings-directory = "/srv/recordings"
      # TODO: make this an optional param and remove the default
      finalize-script = "/etc/jitsi/jibri/record.sh"
   }
   streaming {
      // A list of regex patterns for allowed RTMP URLs. The RTMP URL used
      // when starting a stream must match at least one of the patterns in
      // this list.
      rtmp-allow-list = [
      // By default, all services are allowed
      ".*"
         ]
   }
   ffmpeg {
      resolution = "1920x1080"
      // The audio source that will be used to capture audio on Linux
      audio-source = "alsa"
      // The audio device that will be used to capture audio on Linux
      audio-device = "plug:bsnoop"
   }
   chrome {
      // The flags which will be passed to chromium when launching
      flags = [
      "--use-fake-ui-for-media-stream",
      "--start-maximized",
      "--kiosk",
      "--enabled",
      "--disable-infobars",
      "--autoplay-policy=no-user-gesture-required"
      ]
   }
   stats {
      enable-stats-d = true
   }
   webhook {
      // A list of subscribers interested in receiving webhook events
      subscribers = []
   }
   jwt-info {
      // The path to a .pem file which will be used to sign JWT tokens used in webhook
      // requests. If not set, no JWT will be added to webhook requests.
      # signing-key-path = "/path/to/key.pem"

      // The kid to use as part of the JWT
      # kid = "key-id"

      // The issuer of the JWT
      # issuer = "issuer"

      // The audience of the JWT
      # audience = "audience"

      // The TTL of each generated JWT.  Can not be less than 10 minutes.
      # ttl = 1 hour

   }

   call-status-checks {
      // If all clients have their audio and video muted and if Jibri does not
      // detect any data stream (audio or video) comming in, it will stop
      // recording after NO_MEDIA_TIMEOUT expires.
      no-media-timeout = 30 seconds

      // If all clients have their audio and video muted, Jibri consideres this
      // as an empty call and stops the recording after ALL_MUTED_TIMEOUT expires.
      all-muted-timeout = 10 minutes

      // When detecting if a call is empty, Jibri takes into consideration for how
      // long the call has been empty already. If it has been empty for more than
      // DEFAULT_CALL_EMPTY_TIMEOUT, it will consider it empty and stop the recording.
      default-call-empty-timeout = 30 seconds

   }
}

anther questions how to uninstall jibri from server to try instll it again
i think of this as ip 1.2.3.4 is in the example of the conf file

apt-get purge jibri
apt-get autoremove --purge

Before clicking the enter key, check removing packages carefully.

Or you may edit jibri config files which are in /etc/jitsi/jibri/

I try to uninstall and install it again but I face the same error I don`t know where to get the 1.2.3.4 IP while I give it the private IP of my jitsi server.

Have you checked these files?

yes this the file I have mentions before

jibri {
   // A unique identifier for this Jibri
   // TODO: eventually this will be required with no default
   id = ""
   // Whether or not Jibri should return to idle state after handling
   // (successfully or unsuccessfully) a request. A value of ‘true’
   // here means that a Jibri will NOT return back to the IDLE state
   // and will need to be restarted in order to be used again.
   single-use-mode = false
   api {
      http {
      external-api-port = 2222
      internal-api-port = 3333
      }
      xmpp {
      // See example_xmpp_envs.conf for an example of what is expected here
      environments = [
         {
            name = "prod environment"
            xmpp-server-hosts = ["meet.elemental-tech.com"]
            xmpp-domain = "meet.elemental-tech.com"


            control-muc {
               domain = "internal.auth.meet.elemental-tech.com"
               room-name = "JibriBrewery"
               nickname = "jibri-nickname"
            }

            control-login {
               domain = "auth.meet.elemental-tech.com"
               username = "jibri"
               password = "JPwd"
            }

            call-login {
               domain = "recorder.meet.elemental-tech.com"
               username = "recorder"
               password = "RPwd"
            }

            strip-from-room-domain = "conference."
            usage-timeout = 0
            trust-all-xmpp-certs = true
         }
      ]
      }
   }
   recording {
      recordings-directory = "/srv/recordings"
      # TODO: make this an optional param and remove the default
      finalize-script = "/opt/jitsi/jibri/launch.sh"
   }
   streaming {
      // A list of regex patterns for allowed RTMP URLs. The RTMP URL used
      // when starting a stream must match at least one of the patterns in
      // this list.
      rtmp-allow-list = [
      // By default, all services are allowed
      ".*"
         ]
   }
   ffmpeg {
      resolution = "1920x1080"
      // The audio source that will be used to capture audio on Linux
      audio-source = "alsa"
      // The audio device that will be used to capture audio on Linux
      audio-device = "plug:bsnoop"
   }
   chrome {
      // The flags which will be passed to chromium when launching
      flags = [
      "--use-fake-ui-for-media-stream",
      "--start-maximized",
      "--kiosk",
      "--enabled",
      "--disable-infobars",
      "--autoplay-policy=no-user-gesture-required"
      ]
   }
   stats {
      enable-stats-d = true
   }
   webhook {
      // A list of subscribers interested in receiving webhook events
      subscribers = []
   }
   jwt-info {
      // The path to a .pem file which will be used to sign JWT tokens used in webhook
      // requests. If not set, no JWT will be added to webhook requests.
      # signing-key-path = "/path/to/key.pem"

      // The kid to use as part of the JWT
      # kid = "key-id"

      // The issuer of the JWT
      # issuer = "issuer"

      // The audience of the JWT
      # audience = "audience"

      // The TTL of each generated JWT.  Can not be less than 10 minutes.
      # ttl = 1 hour

   }

   call-status-checks {
      // If all clients have their audio and video muted and if Jibri does not
      // detect any data stream (audio or video) comming in, it will stop
      // recording after NO_MEDIA_TIMEOUT expires.
      no-media-timeout = 30 seconds

      // If all clients have their audio and video muted, Jibri consideres this
      // as an empty call and stops the recording after ALL_MUTED_TIMEOUT expires.
      all-muted-timeout = 10 minutes

      // When detecting if a call is empty, Jibri takes into consideration for how
      // long the call has been empty already. If it has been empty for more than
      // DEFAULT_CALL_EMPTY_TIMEOUT, it will consider it empty and stop the recording.
      default-call-empty-timeout = 30 seconds

   }
}

also /opt/jitsi/jibri/launch.sh

  exec /usr/lib/jvm/adoptopenjdk-8-hotspot-amd64/bin/java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -Dconfig.file="/etc/jit>

also
I try to ping from this machine to jitsi server on port 5222 and it response well

Any other file there?

And I don’t think the latest jibri can run using java8, you should be using java 11.

yes these all file in the directory
jibri.conf jibri.conf.save jibri.conf.save.1 jibri.conf.save.2 logging.properties pjsua.config xorg-video-dummy.conf

Which version of jibri is that?
Does /opt/jitsi/jibri/launch.sh looks like:

?

what this part mean ?

-jar /opt/jitsi/jibri/jibri.jar --config "/etc/jitsi/jibri/config.json

and there is no config.json file

What is the output on jibri:

host meet.elemental-tech.com

meet.elemental-tech.com has address my private ip adress
my private ip adress which is not 1.2.3.4

hi, @emrah @damencho the jibri service in running finally but and get messages from all recorders busy while there is know anther recording work.

this is a log of jibri

2022-10-03 08:46:34.119 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2022-10-03 08:46:34.736 INFO: [1] MainKt.setupLegacyConfig#211: Checking legacy config file /etc/jitsi/jibri/config.json
2022-10-03 08:46:34.741 INFO: [1] MainKt.setupLegacyConfig#214: Legacy config file /etc/jitsi/jibri/config.json doesn't exist
2022-10-03 08:46:36.476 INFO: [1] MainKt.main#55: Jibri starting up with id
2022-10-03 08:46:42.348 INFO: [1] JwtInfo$Companion.fromConfig#176: got jwtConfig: {}

2022-10-03 08:46:42.349 INFO: [1] JwtInfo$Companion.fromConfig#186: Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: /etc/jitsi/jibri/jibri.conf: 88: No configuration setting found for key 'signing-key-path'
2022-10-03 08:46:42.940 INFO: [1] MainKt.main#125: Using port 3333 for internal HTTP API
2022-10-03 08:46:42.942 FINE: [19] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2022-10-03 08:46:44.677 INFO: [1] XmppApi.updatePresence#209: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2022-10-03 08:46:44.709 INFO: [1] XmppApi.start#156: Connecting to xmpp environment on 10.165.11.51 with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[10.165.11.51], xmppDomain=meet.elemental-tech.com, baseUrl=null, controlLogin=XmppCredentials(domain=auth.meet.elemental-tech.com, port=null, username=jibri, password=*****), controlMuc=XmppMuc(domain=internal.auth.meet.elemental-tech.com, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.meet.elemental-tech.com, port=null, username=recorder, password=*****), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true, securityMode=null)
2022-10-03 08:46:44.710 INFO: [1] XmppApi.start#174: The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2022-10-03 08:46:44.781 INFO: [1] MainKt.main#152: Using port 2222 for HTTP API
2022-10-03 08:46:44.810 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient.initializeConnectAndJoin#279: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=10.165.11.51 domain=auth.meet.elemental-tech.com hostname=10.165.11.51 port=null username=jibri mucs=[jibribrewery@internal.auth.meet.elemental-tech.com] mucNickname=jibri-nickname disableCertificateVerification=true]
2022-10-03 08:46:44.820 WARNING: [32] MucClient.createXMPPTCPConnectionConfiguration#115: Disabling certificate verification!
2022-10-03 08:46:44.922 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient.initializeConnectAndJoin#341: Dispatching a thread to connect and login.
2022-10-03 08:46:45.719 FINE: [32] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: xmpp-connected:xmpp_server_host:10.165.11.51
2022-10-03 08:46:45.720 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$2.connected#312: Connected.
2022-10-03 08:46:45.720 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient.lambda$getConnectAndLoginCallable$9#637: Logging in.
2022-10-03 08:46:45.882 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$2.authenticated#318: Authenticated, b=false
2022-10-03 08:46:46.047 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$MucWrapper.join#761: Joined MUC: jibribrewery@internal.auth.meet.elemental-tech.com
2022-10-03 08:47:22.670 WARNING: [49] org.jivesoftware.smack.AbstractXMPPConnection.callConnectionClosedOnErrorListener: Connection XMPPTCPConnection[jibri@auth.meet.elemental-tech.com/XJ82bvHmXGp6] (0) closed with error
org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
<stream:error><system-shutdown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>Received SIGTERM</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:829)
2022-10-03 08:47:22.673 FINE: [49] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: xmpp-closed-on-error:xmpp_server_host:10.165.11.51
2022-10-03 08:47:22.674 WARNING: [49] [hostname=10.165.11.51 id=10.165.11.51] MucClient$2.connectionClosedOnError#332: Closed on error:
org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
<stream:error><system-shutdown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>Received SIGTERM</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:829)
2022-10-03 08:47:26.149 FINE: [32] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: xmpp-connected:xmpp_server_host:10.165.11.51
2022-10-03 08:47:26.149 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$2.connected#312: Connected.
2022-10-03 08:47:26.149 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient.lambda$getConnectAndLoginCallable$9#637: Logging in.
2022-10-03 08:47:26.214 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$2.authenticated#318: Authenticated, b=false
2022-10-03 08:47:26.215 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$MucWrapper.join#741: Leaving a MUC we already occupy.
2022-10-03 08:47:31.216 WARNING: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$MucWrapper.leave#716: Error while trying to leave a MUC:
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). StanzaCollector has been cancelled. Waited for response using: AndFilter: (StanzaTypeFilter: Presence, OrFilter: (AndFilter: (FromMatchesFilter (full): jibribrewery@internal.auth.meet.elemental-tech.com/jibri-nickname, PresenceTypeFilter: type=unavailable, MUCUserStatusCodeFilter: status=110), AndFilter: (FromMatchesFilter (ignoreResourcepart): jibribrewery@internal.auth.meet.elemental-tech.com, PresenceTypeFilter: type=error))).
        at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:124)
        at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:104)
        at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:281)
        at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:228)
        at org.jivesoftware.smackx.muc.MultiUserChat.leave(MultiUserChat.java:798)
        at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.leave(MucClient.java:712)
        at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.join(MucClient.java:742)
        at org.jitsi.xmpp.mucclient.MucClient.joinMucs(MucClient.java:361)
        at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$9(MucClient.java:658)
        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)
2022-10-03 08:47:31.226 INFO: [32] [hostname=10.165.11.51 id=10.165.11.51] MucClient$MucWrapper.join#761: Joined MUC: jibribrewery@internal.auth.meet.elemental-tech.com
2022-10-03 08:47:42.878 FINE: [19] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2022-10-03 08:48:42.878 FINE: [19] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2022-10-03 08:48:44.866 INFO: [48] XmppApi.handleJibriIq#236: Received JibriIq <iq xmlns='jabber:client' to='jibri@auth.meet.elemental-tech.com/_902oa0gkP7h' from='jibribrewery@internal.auth.meet.elemental-tech.com/focus' id='amlicmlAYXV0aC5tZWV0LmVsZW1lbnRhbC10ZWNoLmNvbS9fOTAyb2EwZ2tQN2gANEQxQzctNjUASX4i7Qx2oPg=' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' action='start' recording_mode='file' room='correspondingdecreasesaffordtenderly@conference.meet.elemental-tech.com' session_id='efshltkqclcvnxrd' app_data='{"file_recording_metadata":{"share":true}}'/></iq> from environment [MucClient id=10.165.11.51 hostname=10.165.11.51]
2022-10-03 08:48:44.867 INFO: [48] XmppApi.handleStartJibriIq#268: Received start request, starting service
2022-10-03 08:48:44.983 INFO: [48] XmppApi.handleStartService#379: Parsed call url info: CallUrlInfo(baseUrl=https://meet.elemental-tech.com, callName=correspondingdecreasesaffordtenderly, urlParams=[])
2022-10-03 08:48:44.991 INFO: [48] JibriManager.startFileRecording#138: Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://meet.elemental-tech.com, callName=correspondingdecreasesaffordtenderly, urlParams=[]), email='', passcode=null, callStatsUsernameOverride=, displayName=), sessionId=efshltkqclcvnxrd, callLoginParams=XmppCredentials(domain=recorder.meet.elemental-tech.com, port=null, username=recorder, password=*****))
2022-10-03 08:48:45.006 FINE: [48] [session_id=efshltkqclcvnxrd] FfmpegCapturer.<init>#92: Detected os as OS: LINUX
2022-10-03 08:48:49.044 SEVERE: [48] XmppApi.handleStartJibriIq#300: Error starting Jibri service
org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
  (Driver info: chromedriver=106.0.5249.61 (511755355844955cd3e264779baf0dd38212a4d0-refs/branch-heads/5249@{#569}),platform=Linux 5.15.0-48-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 3.16 seconds
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'cic2-virtual-machine', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-48-generic', java.version: '11.0.11'
Driver info: driver.version: ChromeDriver
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
        at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53)
        at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91)
        at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:123)
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
        at java.base/java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
        at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
        at java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
        at java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.base/java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:543)
        at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:126)
        at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:73)
        at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:136)
        at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:543)
        at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:207)
        at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:130)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:181)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:168)
        at org.jitsi.jibri.selenium.JibriSelenium.<init>(JibriSelenium.kt:199)
        at org.jitsi.jibri.selenium.JibriSelenium.<init>(JibriSelenium.kt:167)
        at org.jitsi.jibri.service.impl.FileRecordingJibriService.<init>(FileRecordingJibriService.kt:109)
        at org.jitsi.jibri.service.impl.FileRecordingJibriService.<init>(FileRecordingJibriService.kt:96)
        at org.jitsi.jibri.JibriManager.startFileRecording(JibriManager.kt:139)
        at org.jitsi.jibri.api.xmpp.XmppApi.handleStartService(XmppApi.kt:383)
        at org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq(XmppApi.kt:275)
        at org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq(XmppApi.kt:243)
        at org.jitsi.jibri.api.xmpp.XmppApi.handleIq(XmppApi.kt:225)
        at org.jitsi.xmpp.mucclient.MucClient.handleIq(MucClient.java:542)
        at org.jitsi.xmpp.mucclient.MucClient$3.handleIQRequest(MucClient.java:505)
        at org.jivesoftware.smack.AbstractXMPPConnection$3.run(AbstractXMPPConnection.java:1565)
        at org.jivesoftware.smack.AbstractXMPPConnection$10.run(AbstractXMPPConnection.java:2143)
        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)
2022-10-03 08:49:42.878 FINE: [19] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status

what is would be the problem ?

Chrome crashed. What are the specs for the vm machine running this?

I tried before recording with docker installation and it works fine with me, but after completing the stand-alone installation get this error .
this is my machine specs

Use 8GB of RAM to run chrome with no issues.

Is there already running desktop environment on this server?
If so, jibri cannot run its own desktop.

even if I shutdown the docker instance?
my docker instances now is down

yes. Is there any window manager in “ps aux” output?