Port forwarding

To reach the node and its apps from outside your network, forward these ports on your router to the address shown, which is the virtual IP:
| What it is for | Ports |
|---|---|
| Node management and apps | TCP and UDP 443 |
| Certificates | TCP 80 |
| VPN (WireGuard) | UDP 51820 |
| TCP 25, 465, 587, 993, 4190 | |
| Torrents (qBittorrent) | TCP and UDP 6881 |
| Video calls (Nextcloud Talk) | TCP and UDP 3478 |
Forwarding is what makes the node reachable from the internet. Without it, node management, apps and the VPN only work from inside your network.
Certificates without forwarding
Section titled “Certificates without forwarding”The node falls back to a self-signed certificate, and browsers warn about it. A valid certificate is issued by Let’s Encrypt over TCP 80, so that port has to be forwarded, and the node’s name has to resolve on the internet to your public IP address so Let’s Encrypt can reach it.
The node still gets a valid certificate. It is issued through your fleet account, so it does not depend on any port being forwarded.