waleed truman
waleed truman
yes we use Docker version
I resolved the issue by updating the jitsi-docker\jibri.yml file to add aliases to the network, but there are still no recordings found in ~\.jitsi-meet-cfg\jibri\recordings. before networks: meet.jitsi: after networks: meet.jitsi:...
I launching it by use docker-compose -f docker-compose.yml -f jibri.yml down docker-compose -f docker-compose.yml -f jibri.yml up -d
version: '3.5'
stable-10184
I provided this information earlier. Can you help me with the steps and parameters I need to add to the .env file or the configuration needed to set up recording...
can tell me with what log you need to check and if can provide me with command to get this log
~/.jitsi-meet-cfg/jibri/logs/log.6.txt Jibri 2025-06-16 11:52:44.126 INFO: [1] MainKt.handleCommandLineArgs#188: Jibri run with args [--config, /etc/jitsi/jibri/config.json] Jibri 2025-06-16 11:52:44.306 INFO: [1] MainKt.setupLegacyConfig#213: Checking legacy config file /etc/jitsi/jibri/config.json Jibri 2025-06-16 11:52:44.324 INFO: [1] MainKt.setupLegacyConfig#216:...
=>>>>>docker logs -f jitsi-docker-jitsi-meet-3de7148-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:...