Hello everyone,
I’m currently trying to deploy Openvidu 3 using Docker on a server that operates in Docker host mode. My server also hosts Apache with virtual servers that occasionally redirect to Docker containers. As a result, ports 80 and 443 are occupied. I’m looking to configure a reverse proxy setup, but I’m struggling to find guidance on how to configure the automatic installation of Openvidu to use bridge network mode and how to correctly expose ports.
Could someone please advise on an easier method or provide guidance on configuring Openvidu to operate in bridge network mode within Docker, while managing port exposure effectively behind a reverse proxy setup?
Thank you in advance for any assistance!
Hi @burakcankolay,
Due to the inherent characteristics of WebRTC, the deployment depends on the network host.
Port 443 manages TCP traffic and redirects to HTTP 7880 for OpenVidu services, while for RTMP and TURN proxies through TCP directly for RTMPs and TURN with TLS. (Caddy config file is very descriptive and understandable, you can check it at /opt/openvidu/config/caddy.yaml)
If you remove the apps.layer4 section from /opt/openvidu/config/caddy.yaml, you’ll end up with a plain HTTP server exposed on port 7880 and ports 80 and 443 will not be used by OpenVidu.
This configuration might allow you to point your Apache server to port 7880. Also your Apache server will need to handle TLS!
However, please note that this change will disable RTMP ingress and TURN over TLS. TURN over 443 UDP will still function.
If you have any other questions, please don’t hesitate to ask.
Best regards