If the system firewall is blocking only outbound ports, WebRTC connection will be possible given that the node is on a machine with a public IP not behind a NAT. Also in this case setting-up a STUN/TURN server will help.ģ. If the user's device is behind a NAT instead, connection will not be made. If the system firewall is blocking only inbound ports, the connection is possible only if the user's device is not behind a NAT and has a public IP. A STUN/TURN server is necessary also in this case.Ģ. If the system firewall is blocking all the outbound and inbound ports, the WebRTC connection cannot be established. Note that if the node is not behind a NAT there are the following possible scenarios:ġ. If the node is instead behind a NAT, a STUN/TURN server is necessary for negotiating NAT traversal when establishing peer-to-peer WebRTC communication. If the node is on a public host with an external IP, the communication is established without problems. The WebRTC peer-to-peer communication happens between the user's browser and the node where the web session is started. The node can be theNoMachine server host or any of the remote nodes being part of its multinode environment. For configuring the NoMachine server to use WebRTC see: Ī STUN/TURN server is needed when the node where the web session will be started is behind a NAT. WebRTC is supported since NoMachine version 5.1.40, but it's not enabled by default.
#NOMACHINE FOR UBUNTU HOW TO#
This article is intended to be an example on how to build and configure your own STUN/TURN server in order to use WebRTC for NoMachine web sessions.
0 kommentar(er)
