After browsing the recording url from the recording stop api, the recording video is shown in white, blank and silent frames.If the recording is long enough, it may end up showing that the openvidu server url can not be accessible.
I already confirmed that the recording urls gotten from the API call are able to pass the mp4 files to the broswer which are stored under the /opt/openvidu/recordings.
My guessing is that as the domain name of the openvidu server is configured at the standalone ELB, the openvidu server vm can not acess the public domain name inside the local intra net. As a result, the internal recording service from openvidu/kms can not attend the session as a subcriber, ending up creating the empty recordings.
Any advice on this empty recording issue?
We also found that OPENVIDU_RECORDING_COMPOSED_URL is avaliable for environment configuration. Any chance to help explaining the usesage of this parameter?
Parameter OPENVIDU_RECORDING_COMPOSED_URL exists precisely to solve this problem. If your server does not have access to the recordings layout hosted inside of the server itself by using DOMAIN_OR_PUBLIC_IP, you can specify what domain or public IP should the server use instead.
For example, let’s suppose that my server is accessible from outside networks through public domain my.domain.com. Then I would configure DOMAIN_OR_PUBLIC_IP=my.domain.com. But let’s also suppose that my server is under a masquerade NAT that prevents it to be able to do a loopbback connection using my public domain. Then composed recording won’t work, because by default the recording module is using DOMAIN_OR_PUBLIC_IP to connect to the recording layout and that is not possible from inside the server itself. So I just need to configure OPENVIDU_RECORDING_COMPOSED_URL=127.0.0.1. This way the recording module will access to the layout using my local internal IP and not the public domain.
I have set the OPENVIDU_RECORDING_COMPOSED_URL=http://localhost:5443/dashboard/, following the originl format for the recording url for the reocrding docker image “http://OPENVIDUAPP:MY_SECRET@{my.domain.com}/dashboard/#/layout-best-fit/dry-lavender-mink/MY_SECRET/-1/false”.
But the recording ends up being black, nothing is shown up. If I set the OPENVIDU_RECORDING_COMPOSED_URL=http://localhost:5443/, the recording will show up the “Welcome to openvidu” index page for the openvidu server.
Can you share the openvidu-server log line starting by “Recorder connecting to url”
(Be aware of modifying your secret, that will be included in that URL).
That line has the exact direction used by the recording container to access the recording layout being served by openvidu-server.
I also want to ask about the actual implementation of recording.
For the COMPOSED mode, the actual action maker is the openvdiu server + openvidu recording.
For the INDIVIDUAL mode, the actual action maker is the openvdiu server.
There is nothing related to KMS.
Am I correct?
COMPOSED recordng uses an external module to record multiple streams in a predefined layout. INDIVIDUAL recording uses a KMS module to dump streams on the disk as they come.
For the pro version, the kms and openvidu server are not in the same vm. Is it still possible to store the recordings of the COMPOSED mode and INDIVIDUAL mode in the same place?
Yes. KMS will temporarely store INDIVIDUAL recordings in its own machine, but openvidu-server process will immediately download the generated files to the recording folder when recording stops.
I can confirm that OPENVIDU_RECORDING_COMPOSED_URL is working fine.
Can you post your .env configuration file? (Remember again to hide your secret key and domain)
Maybe there’s somehting wrong in your configuration.
Updated:
In the new version 2.28, if your Openvidu deployment is running in a VM ( in my case a digitalocean droplet ) then set the value for
OPENVIDU_RECORDING_COMPOSED_URL as " https://<domain_name>/dashboard/ "
In my case the above config option OPENVIDU_RECORDING_COMPOSED_URL was not present in the .env file, so if it is not present then add the config option OPENVIDU_RECORDING_COMPOSED_URL in your .env file as: