Whilst Foldr is often installed as an on premise component of your network, most users expect anytime, anywhere access to their files.
Configuring external access to the Foldr Server allows users to work remotely as if they were on the corporate network from anywhere with an internet connection.
In this article we explain the options available for configuring remote access to your Foldr Server.
The most straight-forward method to provide remote access to Foldr is via public IP.
- First, request a dedicated static public IP address from your Internet service provider.
- Next, configure your firewall to route connections from this public IP address to the internal IP address of the Foldr virtual appliance. Only port TCP 443 (for HTTPS) is required open inbound, however we recommend that TCP port 80 (HTTP) is also opened to allow the use of the free signed SSL certificates offered through Let’s Encrypt. If port 80 is not opened, all users will be forced to enter ‘https://’ into a web browser to initiate a connection. For security reasons, all user sessions initiated on HTTP are automatically redirected to HTTPS.
- Finally, create an external DNS host (A) record for ‘foldr’ on the organisation’s public domain. The host record should resolve to your newly created static, public IP address. The external DNS for your public domain is most likely handled by whoever manages your website hosting.
- Users can now connect to Foldr remotely using a memorable and universally accessible address such as foldr.yourdomain.org
You can also provide external access via a reverse proxy / web publishing service should you have one available on your network. A reverse proxy allows you to present multiple internal services via one dedicated IP address.
As the web publishing service / reverse proxy routes connections to the Foldr Server, a dedicated public IP address is not required.
Integration guide for Microsoft’s TMG or ISA reverse proxy. Foldr has also been tested against Microsoft’s ARR reverse proxy and also the Nginx reverse proxy running on Linux systems.
An option for smaller environments is to configure port forwarding on your router/firewall.
Configure inbound TCP 443 and TCP 80 (for HTTPS and HTTP respectively) requests to be forwarded to the internal address of your Foldr Server.
When using this option, only one service within your the network can use HTTPS externally and as such it is not suitable for environments that might be running web servers or web mail.
Foldr can be configured to run on a custom port other than 443 for client access if required. See here for more details.