Hey Rusty, so I have attempted to deploy the docker-compose text found here via Portainer Stacks (my first time!!), but modified it a little bit to include it in an existing docker network (see below). I figured I would keep it all together since I had already allowed the network 172.17.0.0/16 on my Synology Firewall. Question: is it necessary to have NPM to share the same network as my vaultwarden instance?Yes. You can import any cert as long as you have the fullchain (or just a cert) and private key for it. There is no reason why you can't export it from DSM and import it as a "custom" option.
If you are asking while the cert is still on the DSM side, then just use the certificate UI, and expand the certificate dropdown menu. It will list all the services that use it, including all your docker services as those are almost certainly running via the internal reverse proxy. As such, those will be listed in the certificate menu.
If you need a hand, let me know here, in PM or on my private chat (link is on the site where the article is, top right corner).
My problem I am facing now, which appears to be a very common problem for many users, is I am getting a Bad Gateway message on the initial login screen. Perhaps it has something to do with how I configured my network? I'll continue digging in Github!
version: '3' services: app: image: 'jc21/nginx-proxy-manager:latest' network_mode: "bridge" restart: unless-stopped ports: - '4480:80' - '81:81' - '44443:443' environment: DB_MYSQL_HOST: "db" DB_MYSQL_PORT: 3306 DB_MYSQL_USER: "npm" DB_MYSQL_PASSWORD: "npm" DB_MYSQL_NAME: "npm" volumes: - /volume1/docker/nginxproxymanager/data:/data - /volume1/docker/nginxproxymanager/letsencrypt:/etc/letsencrypt depends_on: - db db: image: 'jc21/mariadb-aria:latest' network_mode: "bridge" restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes: - /volume1/docker/nginxproxymanager/data/mysql:/var/lib/mysql