jibri enabling on docker

[baby-leo]

i have installed the manual jitsi-meet-docker and it is working, but the recording feature is not working and i have not configure anything according to jibri, how can i configure the recording feature on docker?

[saghul]

You can start here: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker#recording--live-streaming-configuration-with-jibri

[baby-leo]

i have seen this config, but i am not sure how to configure it, i have added ENABLE_RECORDING=1 in to the .env file , and i have started the docker services by this docker compose -f docker-compose.yml -f jibri.yml up -d but still the recording is not working

[saghul]

Not working, how? Do you see errors in the Docekr output? Do you get the UI option to record?

[baby-leo]

i do not get any error messages, but i do not get the UI option to record on the browser

[saghul]

Check the Jibri and Prosody container logs please.

[baby-leo]

here is my docker jibri log
`docker logs docker-jitsi-meet-stable-9457-2-jibri-1
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-jibri: applying...
[fix-attrs.d] 10-jibri: exited 0.
[fix-attrs.d] done.
[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...
No AUTOSCALER_URL defined, leaving autoscaler sidecar disabled
[cont-init.d] 10-config: exited 0.
[cont-init.d] done.
[services.d] starting services
icewmbg: Can't open display: :0. X must be running and $DISPLAY set.
[services.d] done.
IceWM: Can't open display: :0. X must be running and $DISPLAY set.
11:50:44.203: icewm-session: icewm exited with status 1.
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux 4d23f099fd91 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-35-generic root=UUID=09436a9e-c69c-40ad-9924-04a05e3f7b43 ro quiet splash
xorg-server 2:21.1.7-3+deb12u7 (https://www.debian.org/support)
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/xorg.log", Time: Mon Oct 14 11:50:44 2024
(++) Using config file: "/etc/jitsi/jibri/xorg-video-dummy.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
[1014/115044.668538:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[1014/115044.668467:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[1014/115044.668711:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[1014/115044.676489:INFO:policy_logger.cc(144)] :components/policy/core/common/config_dir_policy_loader.cc(113) Found mandatory policy file: /etc/opt/chrome/policies/managed/managed_policies.json
[1014/115044.676635:INFO:policy_logger.cc(144)] :components/policy/core/common/config_dir_policy_loader.cc(118) Skipping recommended platform policies because no policy file was found at: /etc/opt/chrome/policies/recommended
[1014/115044.714985:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[1014/115044.723957:WARNING:sandbox_linux.cc(418)] InitializeSandbox() called with multiple threads in process gpu-process.
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Jibri 2024-10-14 11:50:45.402 INFO: [1] MainKt.handleCommandLineArgs#188: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Jibri 2024-10-14 11:50:45.568 INFO: [1] MainKt.setupLegacyConfig#213: Checking legacy config file /etc/jitsi/jibri/config.json
Jibri 2024-10-14 11:50:45.591 INFO: [1] MainKt.setupLegacyConfig#216: Legacy config file /etc/jitsi/jibri/config.json doesn't exist
Jibri 2024-10-14 11:50:46.046 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#234: FallbackSupplier: checking for value via suppliers:`

[IlyaIvanov78]

Hi! If you use some internal resources on main page such images that mounts from your internal network jibri will not work because it uses Selenium and if it can't load something on the page - it crashes on timeout