Hi All,
I have Openvidu deployed to AWS, its working fine, except one thing lately.
In the past few days, all of the recordings has a “Can’t update chrome” error panel on the top right side, as attached!
Have anyone else experienced this and might have solution?
Thanks
Hi!
That is a strange pop up. First time I see it. After some light research, I think we have found a way of avoiding that dialog to be automatically opened by Chrome inside the recording module (using a special flag). The fix is currently in openvidu master branch (Recording container scripts updated with flag --simulated-outdated-no-au · OpenVidu/openvidu@5874870 · GitHub)
You can try building the docker container image from the master branch, and use it in your deployment to at least verify you don’t get that pop up anymore.
To compile the openvidu-recording docker image, simply run this commands:
git clone https://github.com/OpenVidu/openvidu
cd openvidu/openvidu-server/docker/openvidu-recording
./create_image.sh ubuntu-20-04 88.0.4324.146-1 YOUR_CUSTOM_TAG
This will make available in your local machine a new Docker image openvidu/openvidu-recording:YOUR_CUSTOM_TAG
Then you can declare it as an openvidu-server configuration property like this, so openvidu-server uses it instead of the default one:
-DOPENVIDU_RECORDING_VERSION=YOUR_CUSTOM_TAG
Two more things:
If you build the container using 88.0.4324.146-1 as the second parameter of script ./create_image.sh (that is the internal Chrome version, as declared in the code snippet above) you won’t get the pop up, as it is the latest release!. To force the pop up to appear, you can try building the image using an older version. You have all Chrome release version numbers perfectly listed here: UbuntuUpdates - PPA package updates. For example, 80.0.3987.78-1 belongs to a 1 year old release.
Maybe the master version of the recording container is not completely compatible with OpenVidu 2.15.0. If you see strange behaviors, try upgrading to OpenVidu 2.16.0 and then performing the test with your custom built container.
Best regards.
Hi @pabloFuente
Thanks for your answer!
I have deployed the app (2.16.0.) to AWS using the Cloudformation template, so I don’t have my own docker container image to deploy.
Regards,
Balint
You can build the docker image and deploy it to Docker Hub.
Then, in OPENVIDU_RECORDING_VERSION in .env file you can configure the docker image published in your own Docker Hub account.
Regards