OpenVidu 3.2.0

Azure deployments now available in OpenVidu

Changelog

Azure deployments (Beta)

OpenVidu now supports native deployments in Microsoft Azure. You can now deploy in Azure by using ARM templates:

• OpenVidu Single Node COMMUNITY
• OpenVidu Single Node PRO
• OpenVidu Elastic
• OpenVidu High Availability

During version 3.2.0, Azure deployments will be considered in Beta.

New Azure recording tutorials

OpenVidu deployments in Azure use Azure Blob Storage to store recordings (instead of S3). For this reason, we have extended our recording tutorials with Azure Blob Storage compatible examples. You can find them in the following links:

• Recording Basic Azure
• Recording Advanced Azure

OpenVidu Single Node PRO

OpenVidu Single Node PRO is a new type of OpenVidu deployment targeting users that want to deploy OpenVidu as a single-node setup but that still want the **2x performance boost and the [advanced observability](https://openvidu.io/3.2.0/docs/self-hosting/production-ready/observability)** provided by multi-node OpenVidu PRO deployments.

External proxy configuration

By default, OpenVidu is deployed with an internal Caddy server to configure and manage SSL certificates. However, there are certain scenarios where using an external proxy might be preferable:

• You wish to manage SSL certificates manually
• A specific proxy server is required for enhanced security
• You need to integrate a proxy server already in your infrastructure

For any of these cases, now all OpenVidu deployments allow configuring external proxies. You can find the instructions to do so in this how-to guide.

LiveKit stack updated to v1.8.4

OpenVidu 3.2.0 is now based on LiveKit v1.8.4, which includes several improvements and bug fixes. You can find the release notes here.

OpenVidu installer improvements

Some users have reported issues when installing OpenVidu, which were finally caused by old versions of Docker and/or Docker Compose, which resulted in very obscure errors. The OpenVidu installer now checks both versions and displays a descriptive error message if they are incompatible.

OpenVidu Angular Components

(See Angular Components documentation)

• Virtual Backgrounds improvements: More efficient use of resources by reusing the existing context. Avoid video flickering when changing the background. Improved resource reallocation management for smoother rendering. Contribution to LiveKit’s track-processors-js package (PR 86) resolving an issue affecting its dependencies.
• Fixed panel reopening issue with [ovAdditionalPanels](https://openvidu.io/3.2.0/docs/reference-docs/openvidu-components-angular/directives/AdditionalPanelsDirective.html) directive. Custom panels created with ovAdditionalPanels would not reopen correctly after switching between default panels (activities, participants or chat). Now, returning to a custom panel restores it as expected without closing all panels.
• Minor style fixes.

Deployment bug fixes

• OpenVidu On Premises deployments that made use of v2compatibility module had a wrong configuration affecting the S3 MinIO bucket. This could cause issues when recording sessions from your OpenVidu v2 application. This is now fixed.
• Wrong Caddy configuration in OpenVidu High Availability deployments made some services not reachable in specific scenarios of fault tolerance. This is now fixed.

Breaking changes

• For OpenVidu On Premises deployments, the default S3 bucket in MinIO has been renamed from app-data to **openvidu-appdata (in Single Node and Elastic deployments) and from cluster-data to `openvidu-clusterdata`** (in High Availability deployments).
• Port rules in OpenVidu High Availability with Network Load Balancer have changed. Check the port rules from the installation instructions.

Stay tuned for next iterations! You can follow us on 𝕏 and a Star in GitHub is always welcome :)