# Set GARBAGE\_INTERVAL on 2.12 version

**URL:** <https://openvidu.discourse.group/t/set-garbage-interval-on-2-12-version/3286>\
**Category:** Issues with deployment\
**Tags:** v2\
**Created:** [August 9, 2021, 1:30pm UTC](https://openvidu.discourse.group/t/set-garbage-interval-on-2-12-version/3286 "2021-08-09T13:30:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![vitalino](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/vitalino/32/1624_2.png) [@vitalino](https://openvidu.discourse.group/u/vitalino)\
**Post date:** [August 12, 2021, 8:00pm UTC](https://openvidu.discourse.group/t/set-garbage-interval-on-2-12-version/3286/6 "2021-08-12T20:00:52Z")

</div>

I tried with version 2.19, 2.18, and 2.17. Same error.

But, i did a workaround based on reply of @pabloFuente in this issue:

> [@Blank Recordings](https://openvidu.discourse.group/t/blank-recordings/1829):
>
> After browsing the recording url from the recording stop api, the recording video is shown in white, blank and silent frames.If the recording is long enough, it may end up showing that the openvidu server url can not be accessible. I already confirmed that the recording urls gotten from the API call are able to pass the mp4 files to the broswer which are stored under the /opt/openvidu/recordings. My guessing is that as the domain name of the openvidu server is configured at the standalone ELB,…

I set the variable with this config:

`OPENVIDU_RECORDING_COMPOSED_URL=http://127.0.0.1`

And on host OpenVidu server 2.19, i configured a Apache to serve the custom layout.

Now, recording with OpenVidu 2.19 is running fine.

---

_[View the full topic](https://openvidu.discourse.group/t/set-garbage-interval-on-2-12-version/3286)._