use custom ports, otherwise your entire host machine will be serving up 80/443 instead of just your docker container (since Bitwarden automatically maps 80 and 443 to their default ports)

Isolating the cloudflare tunnel directly into your Bitwarden container for ports 443/80 allowed use for your dynamic IP allocated by your ISP using a custom domain name and subdomain Using cloudflare SSL certificates instead of the certbot certs (15 year shelf life) Using CloudFlare tunnels to prevent network open ports Bitwarden has its own user account with restricted access on host machine Official Bitwarden docker image running in a docker container on Windows Desktop This post has helpful info on how to get the following configuration: This is to help you alongside it, as I ran into many challenges not covered. I want to start of by saying, this does not replace the official Bitwarden docs. This also assumes you already have an A record which points to your root domain name to your own public IP.This guide also assumes you have a cloudflare account (free tier), and are using it to host your domain name.Throw that monitor away and stick your server in a corner, and just RDP into it for ease of use (: If you're getting into self hosting stuff on Windows, just get Windows Pro.