# After upgrading to 2.17.0 past recordings do not work **URL:** \ **Category:** Issues with deployment\ **Tags:** bug, v2\ **Created:** [March 11, 2021, 1:56pm UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803 "2021-03-11T13:56:19Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\ **Post date:** [March 11, 2021, 1:56pm UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803/1 "2021-03-11T13:56:19Z")
Hello, Release 2.17.0 comes with an **unexpected breaking change**. This affects you if these 3 conditions are all fulfilled: 1. **You are using the recording feature** 2. **You want to upgrade your existing 2.16.0 stack to 2.17.0** _(new stacks are NOT affected)_ 3. **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](https://hub.docker.com/r/openvidu/openvidu-server) and [openvidu-server-pro](https://hub.docker.com/r/openvidu/openvidu-server-pro) has been released. Update the tag in OpenVidu CE ([this line](https://github.com/OpenVidu/openvidu/blob/master/openvidu-server/deployments/ce/docker-compose/docker-compose.yml#L25)) or OpenVidu PRO ([this line](https://github.com/OpenVidu/openvidu/blob/master/openvidu-server/deployments/pro/docker-compose/openvidu-server-pro/docker-compose.yml#L25)) 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](https://github.com/OpenVidu/openvidu/issues/615) ---
**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\ **Post date:** [March 11, 2021, 1:56pm UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803/2 "2021-03-11T13:56:54Z")
---
**Author:** ![Jimahn.Park](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@Jimahn.Park](https://openvidu.discourse.group/u/Jimahn.Park)\ **Post date:** [April 2, 2021, 7:10am UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803/3 "2021-04-02T07:10:15Z")
my openvidu is v.2.17 in spite of updating ‘image: openvidu/openvidu-server-pro:2.18.0-beta2’ on docker-compose.yml, i can not still record ‘composed type’, individual is ok. ---
**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\ **Post date:** [April 2, 2021, 10:53am UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803/4 "2021-04-02T10:53:01Z")
The version with the fix is 2.17.1. Please, use that and confirm recordings are reachable with that version number. ---
**Author:** ![mrussiello](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@mrussiello](https://openvidu.discourse.group/u/mrussiello)\ **Post date:** [April 7, 2021, 2:39pm UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803/5 "2021-04-07T14:39:07Z")
Sorry, I’m not sure how to get the 2.17.1 image onto my EC2 server. I am using the AWS image of OpenVidu CE. I need to upgrade to 2.17.1 from 2.17.0. Can I just use the upgrade instructions at [OpenVidu Docs](https://docs.openvidu.io/en/2.17.0/deployment/upgrading/) ? ---
**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\ **Post date:** [April 7, 2021, 5:29pm UTC](https://openvidu.discourse.group/t/after-upgrading-to-2-17-0-past-recordings-do-not-work/2803/6 "2021-04-07T17:29:39Z")
Hi, It is in fact a very straightforward process. SSH into your AWS machine (the OpenVidu Server Pro node) and then: `sudo -s` (root user) `cd /opt/openvidu` (go to OpenVidu installation path) Modify file `docker-compose.yml`, updating the tag of openvidu/openvidu-server-pro image from: `image: openvidu/openvidu-server:2.17.0` to `image: openvidu/openvidu-server:2.17.1` And then run `./openvidu restart`, at path `/opt/openvidu` This will upgrade your openvidu-server-pro to the patched version.