The Helm Files service (powered by Nextcloud) is available to users who first set up port forwarding on their router and enable the Files service. The exact steps to do so depend on the router you have. We’ve linked to directions below for some of the most common ones.
Additionally, in order to access your Helm's Files service while your client device is connected to the same local network as your Helm, your router must support NAT hairpinning (also known as NAT reflection or NAT loopback). Hairpinning enables one machine on the local network to access another machine on the local network via the external/public IP address of your router, following the same port-forwarding that is configured to provide access for machines connecting from the Internet.
Before setting up port forwarding, enable the Files service by going to Services in the Helm app and toggling File Storage and Access on.
Steps to implement port forwarding
- Login to your router. Typically, there is a web interface for this.
- Access the page with IP addresses and devices connected to your router. Access router help file for name of the page with this information, e.g. DHCP table.
- Identify your Helm server by finding the IP address or MAC address for the Helm on your router. You can find this information from the Helm app by going to Menu > Helm > Status (under Settings)
- On your router, reserve the IP address issued for the Helm. This step is unique to your router, but could be as simple as selecting a "reserve the IP address" button. You may also need to find the "reserve DHCP or IP address" page and use the IP from Step 3 to reserve this address.
- Access page on router for port forwarding.
- Enter port 9443 for both external and internal ports with TCP as the protocol and forward to the IP address from Step 3.
If you do not see your router listed and need steps, check your router for its make and model then search for “port forwarding steps” specific to that router.
For further questions about port forwarding or the initial Files setup, please reach out to firstname.lastname@example.org.
At this time, we are working on known issues with federated file sharing and versioning. We are also working on a minor issue affecting users who toggle the Files service On, Off, and back On. While a reboot resolves this issue, if you intend to use the Files service we recommend leaving it on until we push a fix. For further questions about this, please reach out to our Support team. We will update users when these are resolved.