You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/openvidu-pro/deployment/on-premises.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -92,9 +92,9 @@ Once you have your instances ready, be sure to meet the following criteria in th
92
92
-**Open these ports** ([here](#close-ports-in-media-nodes-to-avoid-external-attacks) you have an UFW sample to configure a firewall)
93
93
94
94
- **22 TCP**: to connect using SSH to admin OpenVidu.
95
-
- **80 TCP**: to allow OpenVidu Server Pro Node downloading recording files.
96
95
- **40000 - 65535 TCP+UDP**: used by Kurento Media Server to establish media connections.
97
-
- **8888 TCP**: Kurento Media Server handler listens on port 8888. <strong style="color: #990000">WARNING!!</strong> Port 8888 **must only be accessible for OpenVidu Server Pro instance**. Access trough this port must be restricted from the Internet, or anyone could spy your sessions.<br><br>
96
+
- **8888 TCP**: Kurento Media Server handler listens on port 8888. <strong style="color: #990000">WARNING!!</strong> Port 8888 **must only be accessible for OpenVidu Server Pro instance**. This port must be closed to the Internet, or anyone could spy your sessions.
97
+
- **80 TCP**: to allow OpenVidu Server Pro Node downloading recording files. <strong style="color: #990000">WARNING!!</strong> Port 80 **must only be accessible for OpenVidu Server Pro instance**. This port must be closed to the Internet, or anyone could download your recordings.<br><br>
98
98
99
99
-**Close all other ports**: this is VERY important to avoid external attacks to OpenVidu internal services. Check troubleshooting section [Close ports in Media Nodes to avoid external attacks](#close-ports-in-media-nodes-to-avoid-external-attacks) to learn more about this.
0 commit comments