NextCloud Talk Recording Server

bikesh.mhz · April 11, 2025, 9:56am

Hi,
Did any of you guys have in installed the Nextcloud talk recording server? If you have installed please share the installation process. I am new to Nextcloud environment. And I wanted to install the recording server for Talk. But Sadly there is not enough documentation on installing the recording server. I have tried installing the server but got the error as below:
/tmp/recording$ PYTHONPATH=/tmp/recording/src python3 -m nextcloud.talk.recording --config /etc/nextcloud-talk-recording/server.conf
No configured backends

Serving Flask app ‘nextcloud.talk.recording.Server’
Debug mode: off
INFO:werkzeug:WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
Running on all addresses (0.0.0.0)
Running on http://127.0.0.1:8000
Running on http://192.168.0.11:8000
INFO:werkzeug:Press CTRL+C to quit
INFO:werkzeug:192.168.0.11 - - [11/Apr/2025 09:44:42] “GET /api/v1/welcome HTTP/1.1” 200 -
INFO:werkzeug:192.168.0.11 - - [11/Apr/2025 09:44:50] “GET /api/v1/welcome HTTP/1.1” 200 -
INFO:nextcloud.talk.recording.Server:Start recording: https://nextcloud.abc.com/ 432c66ik
INFO:werkzeug:192.168.0.11 - - [11/Apr/2025 09:45:03] “POST /api/v1/room/432c66ik HTTP/1.1” 200 -
E: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
xcb_connection_has_error() returned true

xcb_connection_has_error() returned true
ERROR:nextcloud.talk.recording.Server:Failed to start recording: https://nextcloud.abc.com/ 432c66ik
Traceback (most recent call last):
File “/tmp/recording/src/nextcloud/talk/recording/Server.py”, line 365, in _startRecordingService
service.start(actorType, actorId)
File “/tmp/recording/src/nextcloud/talk/recording/Service.py”, line 196, in start
self._participant.joinCall(self.token)
File “/tmp/recording/src/nextcloud/talk/recording/Participant.py”, line 507, in joinCall
self.seleniumHelper.executeAsync(f’‘’
File “/tmp/recording/src/nextcloud/talk/recording/Participant.py”, line 419, in executeAsync
result = self.driver.execute_async_script(script)
File “/home/sgdg/.local/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py”, line 550, in execute_async_script
return self.execute(command, {“script”: script, “args”: converted_args})[“value”]
File “/home/sgdg/.local/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py”, line 429, in execute
self.error_handler.check_response(response)
File “/home/sgdg/.local/lib/python3.10/site-packages/selenium/webdriver/remote/errorhandler.py”, line 232, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message: Timed out after 30000 ms
Stacktrace:
RemoteError@chrome://remote/content/shared/RemoteError.sys.mjs:8:8
WebDriverError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:197:5
ScriptTimeoutError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:722:5
evaluate.sandbox/timeoutPromise</scriptTimeoutID<@chrome://remote/content/marionette/evaluate.sys.mjs:97:11
notify@resource://gre/modules/Timer.sys.mjs:49:17

I am getting the “selenium.common.exceptions.TimeoutException: Message: Timed out after 30000 ms” even in docker container as well.

Hoping for your help gyus.
Thanks in advance.

j-ed · April 11, 2025, 1:05pm

The installation process is described on GitHub:

github.com/nextcloud/nextcloud-talk-recording

docs/installation.md

main

<!--
  - SPDX-FileCopyrightText: 2023 Nextcloud GmbH and Nextcloud contributors
  - SPDX-License-Identifier: AGPL-3.0-or-later
-->
# Installation

The recording server requires an HPB (High Performance Backend for Talk) to be setup. However, it is recommended to setup the recording server in a different machine than the HPB to prevent their load to interfere with each other. Moreover, as the recording server requires some dependencies that are not typically found in server machines, like Firefox, it is recommended to use its own "isolated" machine (either a real machine or a virtual machine). A container would also work, although it might require a special configuration to start the server when the container is started.

In practice the recording server acts just as another Talk client, so it could be located anywhere as long as it can connect to the Nextcloud server and to the HPB, in the later case either directly or through the TURN server. Nevertheless, for simplicity and reliability, it is recommended for the recording server to have direct access to the HPB (so if the HPB is running in an internal network the recording server should be setup in that same internal network as the HPB).

## Hardware requirements

As a quick reference, with the default settings, in an AMD Ryzen 7 3700X 8-Core Processor (so 16 threads, theoretically a maximum usage of 1600% CPU) recording a single call uses 200% CPU (mostly to encode the video). The recording server provides [a benchmark tool](encoders.md) that can be used to check the load with different encoding settings and find out an approximation of the load that will occur when recording a call. Nevertheless in a real recording there is an additional load from the WebRTC connections, the rendering of the browser and so on, but in general the encoding uses the most CPU.

Regarding RAM memory the encoding does not use much, and it should be calculated based on how many simultaneous recordings and therefore browsers are expected. For a single browser 2 GiB should be enough, although it would be recommended to play safe and have more if possible due to the increasing memory requirements of browsers (and also if the calls to be recorded include a lot of participants).

Finally disk size will also depend on the number of simultaneous recordings, as well as the quality and codec used, which directly affect the size of the recording. In general the recorded videos will stay on the recording server only while being recorded and they will be removed as soon as they are uploaded to the Nextcloud server. However, if the upload fails the recorded video will be kept in the recording server until manually removed.

## Installation type

Diese Datei wurde abgeschnitten. Original zeigen

bikesh.mhz · April 11, 2025, 2:41pm

I followed the same steps as mentioned in the GitHub but no success.