Official docs does not have Coturn outside of the infrastructure, Coturn and nginx are in the Master Node.
Two possible things that are happening in this scenario:
- Kurento Media Server does not have access to Coturn to autodiscover its public IP and it is sending candidates with private IPs
- Browsers are accessing to a wrongly configured Coturn, so they also can’t discover its public IP. How are you configuring the Coturn Server in the browser side.
In this scenario, what I would do is:
- If “SI Video Master” and “SI Video Node” are in the same network, put in
/opt/openvidu/.env file a variable named COTURN_IP with the private IP of the “SI Video Nginx Coturn VM”. Port 3478 TCP/UDP should be accessible to the “SI Video Node”, so it can autodiscover its public IP.
- Configure in Coturn some fixed credentials and configure in OpenVidu Call the deployed Coturn with its domain name and its credentials: GitHub - OpenVidu/openvidu-external-coturn
The instructions on the guide don’t deploy Nginx and Coturn in a different machine, why are you doing that?. It would be easier to you if you just deploy nginx and Coturn next to OpenVidu Pro in the same machine as the documentation says.