

obeviously with aportforwarding on port 60000 on my router). tried to start certbot manually (docker run -it -rm -name certbot -p 60000:80. during the installation I've tried to create the certificate with Let's encrypt - it fails because port 80 is in use alreadyĢ.

Without SSL the installation is working fine. The created data is at /share/CACHEDEV1_DATA/Container/bwdata The installation file (bitwarden.sh) is placed at /share/CACHEDEV1_DATA/Container The Installation of Bitwarden was successfull, eventhough it took me hours to find a way to do so - I had to do it via SSH on the NAS - I was never using SSH on the NAS before. (Sub-)Domain registered at all-inkl - I'm using the Premium package whcih allows me to modify SSL and DNS entries, etc.ĭDNS configured via all-inkl, but I can't create a certificate from all-inklĭDNS configured on my NAS (qnap mycloudservices)įritzBox 7490 (Portfording http 5xxx0 -> 5xxx0 and https 5xxx1 to 5xxx1)īitwarden (using multiple docker container, which are being merged via Docker-Compose) QNAP TS251 (Container Station installed and two Container running) It's working, but I can't manage to have SSL running perfectly. Since two days I'm trying to install Bitwarden onto my TS251.
