Hello,
Release 2.17.0 comes with an unexpected breaking change. This affects you if these 3 conditions are all fulfilled:
- You are using the recording feature
- You want to upgrade your existing 2.16.0 stack to 2.17.0 (new stacks are NOT affected)
- You have existing recordings when performing the upgrade (if there are no recordings when upgrading then this does NOT affect you)
If these 3 conditions are met, after the upgrade recordings won’t be recoverable using REST API (a 500 error will be returned instead).
This affects both OpenVidu CE and OpenVidu PRO (and both normal storage or S3 storage for PRO). If you are experiencing this bug, there is a simple fix. A new 2.17.1 patch version of containers openvidu-server and openvidu-server-pro has been released.
Update the tag in OpenVidu CE (this line) or OpenVidu PRO (this line) at your OpenVidu Server host installation’s path (by default /opt/openvidu/docker-compose.yml
) and restart the service with ./openvidu restart
Related GitHub issue: Unable access recordings from inspector after upgrading to v2.17.0 · Issue #615 · OpenVidu/openvidu · GitHub