Bitwarden docker container12/19/2023 ![]() (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. Then - just as I'm pulling my hair out - I'll go for a run or walk the dog and come back to find that everything is working again.Since two days I'm trying to install Bitwarden onto my TS251. I'll restart my router, the NAS, and restart the SWAG docker a few times. The log file will start saying "Certificate Not Found, etc". I can no longer access BW using the duckdns link. I can access BW from my internal computers, my phone, and my work computer. I will check the SWAG log and it will say "Server Ready" for all of my duckdn subdomains. I've properly forwarded my ports and I'm confident that I've correctly configured SWAG, BitWarden, and the necessary. Has anybody experienced an issue where SWAG (formerly "LetsEncrypt") will inexplicably stop resolving the secure connection when using duckdns? I've been setting up Bitwarden using SWAG as my reverse proxy.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |