# Nginxproxymanager cert for vaultwarden docker-compose

**URL:** <https://vaultwarden.discourse.group/t/nginxproxymanager-cert-for-vaultwarden-docker-compose/3049>\
**Category:** Help\
**Created:** [November 3, 2023, 1:47am UTC](https://vaultwarden.discourse.group/t/nginxproxymanager-cert-for-vaultwarden-docker-compose/3049 "2023-11-03T01:47:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![damn](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/damn/32/1217_2.png) [@damn](https://vaultwarden.discourse.group/u/damn)\
**Post date:** [November 3, 2023, 1:47am UTC](https://vaultwarden.discourse.group/t/nginxproxymanager-cert-for-vaultwarden-docker-compose/3049/1 "2023-11-03T01:47:40Z")

</div>

Hi,  
I spent 3 days trying to figure out how to get https running in vaultwarden (docker-compose) by myself, but still without luck…

I’m running Proxmox with a bunch of lxc containers…

One is running NPM reverse proxy (nginx-proxy-manager) which manages my dyn-dns adresses and my certs and redirects to other containers.

In another container I installed vaultwarden and exposed a port XXXX to port 80 of the docker-compose container specified in the docker-compose.yml.

The NPM is holding a cert and I added a proxy host pointing from the dyndns domain to the ip of the vaultwarden container with the exposed port (e.g. [mydyndns.com](http://mydyndns.com) to 192.168.1.2:XXXX).

This sort of configuration is working for a bunch of other containers, but no matter what I do, it is still not working with Vaultwarden! What am I doing wrong? am I missing something?

Is it right that Vaultwardens https should be bound to internal port 80 of the container, or is there a 443 port available? I think I also tested it, but only to be sure I configured the docker-compose.yml right…

any help appreciated 'cause I’m already pulling out my hair because it’s so frustrating that it seems I can’t get it to work by myself…

ahh and just to mention it… vaultwarden and NPM containers are both privileged lxc containers…

cheers,  
Dan

---

<div class="post-metadata">

**Author:** ![damn](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/damn/32/1217_2.png) [@damn](https://vaultwarden.discourse.group/u/damn)\
**Post date:** [November 3, 2023, 2:26am UTC](https://vaultwarden.discourse.group/t/nginxproxymanager-cert-for-vaultwarden-docker-compose/3049/2 "2023-11-03T02:26:47Z")

</div>

Forgot to mention that I also already tried to adapt the answer from this [post](https://vaultwarden.discourse.group/t/vaultwarden-and-nginx-proxy-manager/1307/23) to my proxy config, but this also didn’t help

---

<div class="post-metadata">

**Author:** ![damn](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/damn/32/1217_2.png) [@damn](https://vaultwarden.discourse.group/u/damn)\
**Post date:** [November 4, 2023, 10:30am UTC](https://vaultwarden.discourse.group/t/nginxproxymanager-cert-for-vaultwarden-docker-compose/3049/3 "2023-11-04T10:30:26Z")

</div>

Ok I finally managed to get it running…

I completely deleted the vaultwarden proxmox container, then used [this tutorial](https://technium.ch/vaultwarden-lxc-installieren-proxmox-7-tutorial/) to create a new container. I skipped the optional “caddy” part of the tutorial and started the container.

After that I created a new ddns address wihich I added as new proxy host to NPM and pointed it to the container’s IP and created a new letsencrypt cert for the new ddns.

Et voila… a new https secured vaultwarden is up and running 😉