# Issues Upgrading to OV Pro

**URL:** <https://openvidu.discourse.group/t/issues-upgrading-to-ov-pro/3654>\
**Category:** Issues with deployment\
**Tags:** v2\
**Created:** [December 3, 2021, 9:11pm UTC](https://openvidu.discourse.group/t/issues-upgrading-to-ov-pro/3654 "2021-12-03T21:11:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [December 9, 2021, 11:46am UTC](https://openvidu.discourse.group/t/issues-upgrading-to-ov-pro/3654/2 "2021-12-09T11:46:23Z")

</div>

Hello @mrussiello. The unique difference using the built-in STUN/TURN between OpenVidu CE and OpenVidu PRO is that relay candidates in CE connects directly with the media server because both are in the same machine. In OpenVidu PRO relay candidates uses the public IP as relay candidate because it is the sanest default configuration for every environment, but maybe in your case is not working.

I suggest you to add this environment variable in /opt/openvidu/.env:

```auto
COTURN_INTERNAL_RELAY=true

```

This will tell to the Coturn server to use the internal IP as relay candidate to connect to the Media Server.  
Maybe this works, give it a try.

Regards

---

_[View the full topic](https://openvidu.discourse.group/t/issues-upgrading-to-ov-pro/3654)._