OpenVidu 2.28.0: High Availability on premises

2 min readJun 23, 2023



OpenVidu Enterprise HA on premises

It is now possible to deploy OpenVidu Enterprise High Availability in your own servers! Since OpenVidu 2.20.0 we have offered the High Availability deployment option for high demanding environments which require full scalability and fault tolerance. But this option was only available as an AWS deployment. Up until now.

This new deployment option has also brought a brand new architectural solution. This has been done in order to simplify the management of the OpenVidu nodes, the decission on how many Master Nodes (for signaling) and Media Nodes (for video/audio streams) you should launch, and to prepare the ground for future native deployments on Kubernetes. OpenVidu Enterprise HA on premises deployments is now based on a single Node, which includes in a single machine all the components that were splitted between two different machines (a Master Node and a Media Node) before.

OpenVidu Enterprise HA on premises

You can follow the instructions to deploy an OpenVidu Enterprise HA cluster on premises right here.

OpenVidu Components improvements related to language management


  • A new event (onLangChanged) is emitted by VideoconferenceComponent when the application language has changed, so you can act upon a user selecting a different language. See the event here.
  • A new directive (langOptions) is added to customize the language options available in the application. See here.

COTURN update to latest release 4.6.2

See all changelogs since previous version (which was 4.5.2) here.


  • openvidu-node-client: it wasn’t catching errors on “fetch()” request which could potentially affect the application’s error handling
  • openvidu-browser: custom screenshare tracks were not detected as screen. Now they are. Related Issues and PRs: Issue 808, PR 809.
  • Recording: in OpenVidu PRO and OpenVidu ENTEPRISE, in very rare occasions the recording service could return a 404 error when stopping an active recording, instead of the expected 200. This could affect the ongoing session and future recordings for that session. This is now fixed.
  • openvidu-java-client: global configuration paremeter OPENVIDU_WEBRTC_ICE_SERVERS was being overridden by openvidu-java-client when not configuring custom ICE servers, setting an empty array. This made OPENVIDU_WEBRTC_ICE_SERVERS configuration parameter to be ignored. Now this is fixed, and the global parameter will be used if Connection parameter for a custom ICE server is empty.
  • OpenVidu Components: on fullscreen mode, the settings menu (3 dots) was not displayed. Now it is.
  • OpenVidu Components: switching the camera in Android devices was not working properly. This is now fixed.
  • OpenVidu Components: audiomuted and videomuted properties of the components were ignored if local storage values were present. This is fixed now.

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