# IP whitelisting of dashboards breaks composed recording

**URL:** <https://openvidu.discourse.group/t/ip-whitelisting-of-dashboards-breaks-composed-recording/3555>\
**Category:** Issues with deployment\
**Tags:** v2\
**Created:** [November 4, 2021, 2:23pm UTC](https://openvidu.discourse.group/t/ip-whitelisting-of-dashboards-breaks-composed-recording/3555 "2021-11-04T14:23:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/bit/32/1455_2.png) [@Bit](https://openvidu.discourse.group/u/Bit)\
**Post date:** [November 4, 2021, 2:23pm UTC](https://openvidu.discourse.group/t/ip-whitelisting-of-dashboards-breaks-composed-recording/3555/1 "2021-11-04T14:23:05Z")

</div>

OpenVidu Pro 2.17.0 on Ubuntu 20.04

I’m making use of “ALLOWED\_ACCESS\_TO\_DASHBOARD” in the .env and it works as expected apart from an issue whereby composed video recordings come out like this:

 ![image](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/a/aa78ba2fa067748c7abb530720ab5723bf83048d.png)

I’ve tried adding the private IP ranges that we’re using as well as localhost but the issue persists.

Any help much appreciated.

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [November 4, 2021, 9:03pm UTC](https://openvidu.discourse.group/t/ip-whitelisting-of-dashboards-breaks-composed-recording/3555/2 "2021-11-04T21:03:30Z")

</div>

mmm can you try with this in your .env file?:

```auto
OPENVIDU_RECORDING_COMPOSED_URL=http://localhost:5443

```

---

<div class="post-metadata">

**Author:** ![Bit](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/bit/32/1455_2.png) [@Bit](https://openvidu.discourse.group/u/Bit)\
**Post date:** [January 10, 2022, 4:15pm UTC](https://openvidu.discourse.group/t/ip-whitelisting-of-dashboards-breaks-composed-recording/3555/3 "2022-01-10T16:15:40Z")

</div>

Sorry for the very late reply.

I did as you suggested; the error is now:  
 ![image](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/f/f0af93cbdb086aa78a89c9f660caf8ae4f5825c9.png)

Somewhat odd as curl returns the “Welcome to Openvidu Pro” page on that URL.

Edit: I realise that my last line was due to me doing curl from the host rather than the container.

If I change OPENVIDU\_RECORDING\_COMPOSED\_URL to [IP address of the host]:5443 then I get the “Welcome to Openvidu Pro” page in the video instead.

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [January 10, 2022, 5:02pm UTC](https://openvidu.discourse.group/t/ip-whitelisting-of-dashboards-breaks-composed-recording/3555/4 "2022-01-10T17:02:40Z")

</div>

I think it is not possible for recordings right now to works with ALLOWED\_ACCESS\_TO\_DASHBOARD. Since version 2.17.0, recordings occurs on media nodes. So a possible workaround:

1. Remove the `OPENVIDU_RECORDING_COMPOSED_URL` parameter.
2. Put the public IPs of the media nodes in the `ALLOWED_ACCESS_TO_DASHBOARD`. If you don’t have autoscaling, maybe this works for you.

Regards
