![]() The app can be built with grunt: grunt (html files will be in dist/).ĭesktop apps are built with grunt desktop. The easiest way to clone all KeeWeb repos is: put your dh.pem, cert.pem, key.pem to /etc/nginx/external/ĭocker run –name keeweb -d -p 443:443 -p 80:80 -v $EXT_DIR:/etc/nginx/external/ antelle/keeweb.You can download the latest distribution files from gh-pages branch. The app is a single HTML file + a service worker (optionally for offline access). Basic stuff, as well as more advanced operations, should be rather reliable.Įverything you need to host this app on your server is any static file server. The app can run either in browser, or as a desktop app. It doesn’t require any server or additional resources. Note: If you don’t want to create new certificate for all your containers you should use my guide on How to Add Wildcard Certificate.Keeweb webapp is a browser and desktop password manager compatible with KeePass databases. Follow the instructions in the image below. After you click on WebSocket, two Header Names and two Values will be automatically added. Click Create and then, from the drop-down menu, click WebSocket. To do this, go to Control Panel / Login Portal / select your Reverse Proxy then click the Custom Header tab. Note: Some Docker containers like Home Assistant (Not All) need WebSocket activation in order to work over an HTTPS connection. Note: This guide can be applied to all Synology NAS Docker Containers for which you want to use HTTPS/SSL. Synology DSM 7: Access without Port :5001 Note: In the browser address bar don’t forget to add before the link. Now open your browser and type in your HTTPS/SSL certificate, in my case Go back to STEP 1 or you will deal with karma □ Select your Certificate and, from the dropdown menu, select your Certificate again, then click OK. Your new certificate should be mirroring. Go to Control Panel / Security / Certificate / Select the certificate you have previously created at STEP 7, then click Settings. For example, my Bitwarden container is running in localhost on port 5151. This port can vary from container to container. Note: Under Destination, the localhost port will vary depending on the port you used to create your container. After that, add the following instructions: On General area, set the Reverse Proxy Name description: type in Bitwarden or the Description you have already chosen at STEP 5. Follow the instructions in the image below.Īfter you click the Create button, the window below will open. Go to Control Panel / Login Portal / Advanced Tab / click Reverse Proxy. Note: If you fail to create a new certificate try to create a new certificate using your instead using the https connection. If everything goes right, you will see your new certificate in the Certificate area. Follow the instructions in the image below.Īfter you click Done, you will have to wait a few seconds for your new certificate to be created. Type in your email in the Email area, then click Done. or the description name you have previously chosen at STEP 5. Follow the instructions in the image below.Īfter you click Next, on the Domain name area, type in bitwarden. Select Get a certificate from Let’s Encrypt then click Next. I choose “ bitwarden” because I will be using this certificate for my Bitwarden container. Follow the instructions in the image below.Īfter you click Next, select a Description for your certificate. Select Add a new certificate then click Next. Follow the instructions in the image below.Īfter you click Add on STEP 3 a new pop up window will open. Go to Control Panel / Security / Certificate then click the Add tab. Note: If you already own a DDNS, skip this STEP. ![]() Please Support My work by Making a Donation.įollow my step by step guide on how to activate your DDNS on DSM 7įollow my step by step guide on how to activate your DDNS on DSM 6.2.4 ![]() Remember this is a premium article and your support is appreciated. Definitely a guide that you will find extremely useful and will surely help make your experience with Synology NAS devices even more exciting. Today I will teach you how to add a custom Subdomain to your DDNS and use a different one for each of your containers, without worrying about remembering the final port number. And, to continue the series, today I have a new and exciting guide that many of you have been requesting for some time: how to remove the port number at the end of your DDNS address, for example, :5152. You all loved my series of articles on how to use an HTTPS/SSL certificate to secure your Docker containers and make them accessible from anywhere, like my article Synology: How to Allow BitWarden to Work Over an HTTPS Connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |