![]() ![]() This Wiki also assumes you have docker and docker-compose working and you know how to use this. Please note that the setup described in this setup requires a local DNS or split DNS (as described in the above Wiki). The definitions and requirements from the Wiki’s mentioned above apply to this Wiki too. This Wiki assumes you have managed to setup a Caddy reverse proxy as explained in the Wiki Using Caddy as a reverse proxy in a home network by First reading the Wiki Use Caddy for local HTTPS (TLS) between front-end reverse proxy and LAN hosts is helpful but probably not necessary. ![]() There is no need for any other software as Caddy has everything build in to connect the pieces (services) together. ![]() This is specifically interesting for Vaultwarden because without, your passwords will cross your LAN unencrypted. The connections upstream, are also encrypted with the help of the ACME server built into Caddy. This Wiki is a continuation, which results in a setup with Nextcloud and Collabora integrated and Vaultwarden running behind a Caddy reverse proxy with a Let’s Encrypt certificate. In the Wiki Use Caddy for local HTTPS (TLS) between front-end reverse proxy and LAN hosts I described how to add TLS between the downstream reverse proxy and the upstream hosts (services). For quick references, just scroll down to the second post which contains final and complete configuration files. With this setup the connection will be encrypted from A to Z. The frontend Caddy will also issue TLS certificates for the backend LAN connections and renew them periodically. This Wiki contains the info to setup a frontend Caddy reverse proxy service with a Let’s Encrypt authorized TLS certificate and a backend host running a Caddy reverse proxy / webserver which serves Nextcloud with Collabora integrated and Vaultwarden ( formerly Bitwarden_rs).
0 Comments
Leave a Reply. |