Does the Helm require special firewall configuration?

For basic operation of your Helm Personal Server, it is unlikely that updates to your home network's firewall need be made.  However, if you have configured your firewall in a more restrictive manner, such that outbound traffic is denied unless explicit exceptions are made, then you will need to open a few ports for the Helm.

Outbound traffic

If your firewall restricts outbound network traffic, please open the following for the Helm:

• TCP port 80 (HTTP)
• TCP port 443 (HTTPS)
• UDP port 500 (IPsec IKEv2)
• UDP port 4500 (IPsec NAT traversal)

Inbound traffic

For email, calendar, contacts, and administrative access from the Helm mobile app, incoming connections to the Helm Personal Server are routed through its security gateway via an IPsec VPN that is established by the Helm when it starts up (see "How does Helm work?" for more on that).  Thus, for these services, no special configuration must be made for inbound traffic.

For the Helm files service, network traffic is not routed through the security gateway, but directly to the Helm on TCP port 9443.  This requires forwarding of that port from the network's public IP address to the same port on the Helm at its private IP address.  For details, please see "Setting up Files".