And really 443 should be removed if behind a reverse proxy with ssl-offload.įails with bind mount errors for missing. I'm under the impression 80 and 443 should have changed in the docker-compose.yml for the host ports. Synology Reverse Proxy in front of bitwardenīw.:80 -> localhost:8223 (hoping bitwarden redirects on x-forwarded-proto to https)īw.:443 -> localhost:8223 (using certificate on synology for bw. for ssl offload)ĭo you want to use the default ports (80/443): nĭefault ports (80/443) on your reverse proxy: yįrom this point, ports in the docker-compose.yml end up being 80 and 443 which clash with synology's webservers, which I had to manually change to 82 as a workaround.
I'm wondering if my understanding of the prompts is being interpreted wrong for my setup.Ĭurrently I am attempting the following deployment: I've managed to complete an install by manually changing docker-compose.yml as well as creating missing folders.
I've been testing out deployment of bitwarden using the bitwarden.sh script on a Synology DSM.
0 kommentar(er)
