Clarify 55820 behind-port-forward scenario

Author: DavidePrincipi

cluster.rst

@@ -107,17 +107,21 @@ Confirm or enter the leader host name in the ``VPN public address``
 field. An IP address is accepted, too.
 
 Confirm or enter the ``VPN public UDP port`` number. Every worker node
-will connect the leader on that UDP port number.
+will connect the leader on that UDP port number. In most cases, the
+default VPN port, which is ``55820``, should suffice, unless there is a
+network device between the leader and the workers mapping it to a
+different port number.
 
 When the confirmation string is typed, the :guilabel:`I understand,
 promote the node` button becomes active and it is possible to complete the
 node promotion.
 
-The ``Check node connectivity`` checkbox verifies the connection of every
-node with the selected one.  The check might fail due to settings of other
-devices in the network, like port-forwarding. In this case, if you are
-sure the entered configuration is correct, it is possible to disable the
-check: do it at your own risk!
+The ``Check node connectivity`` checkbox verifies the connection of each
+node with the selected one. Since the VPN connection cannot be probed,
+only HTTPS is checked, and it may fail due to settings on other network
+devices, such as port-forwarding. In this case, if you are certain that
+the entered configuration is correct, you have the option to disable the
+check, but proceed at your own risk!
 
 Unreachable leader node
 -----------------------

firewall.rst

@@ -9,9 +9,7 @@ is permitted.
 All other network interfaces are part of a public zone where only specific ports are open.
 By default, NS8 will have the following open ports:
 
-- cluster VPN endpoint, default is 55820 UDP. It can be changed during
-  :ref:`post-installation steps <post-install-steps>` and :ref:`node
-  promotion <node-promotion-section>`
+- Wireguard VPN, 55820 UDP
 - HTTP and HTTPS, 80 and 443 TCP
 - SSH, 22 TCP
 - Cockpit (not installed by default), 9090 TCP