Many users install a variety of web applications in jails on their FreeNAS servers, and often those applications run on non-standard ports like 6789, 8181, 7878, etc. These port numbers are far from intuitive, and the applications often either don't implement HTTPS at all, or make it difficult to configure. A common recommendation to address these issues is to install a separate web server to act as a reverse proxy (allowing you to browse to simpler URLs like http://yourserver/radarr), and also to handle the TLS termination. Although popular web servers like Apache and Nginx can act as reverse proxies, configuration is complex, and neither of them handle the TLS certificates and configuration by default. This guide will cover installing Caddy in its own jail, configuring it to act as a proxy for your other applications, and optionally obtaining TLS certificates from Let's Encrypt and using them to encrypt your communications.
Installation
Installation of Caddy is done using a script. The script and instructions on its usage can be found at:
github.com
Support/Discussion
Questions or issues about this resource can be raised in this forum thread.
Installation
Installation of Caddy is done using a script. The script and instructions on its usage can be found at:
GitHub - danb35/freenas-iocage-caddy: Script to install Caddy V2 in a FreeNAS jail
Script to install Caddy V2 in a FreeNAS jail. Contribute to danb35/freenas-iocage-caddy development by creating an account on GitHub.
Support/Discussion
Questions or issues about this resource can be raised in this forum thread.