Fixup previous change

Francisco Pombal 2019-12-27 13:01:16 +00:00
parent 4b6c75b455
commit 2b3afa3ec0

@ -49,13 +49,16 @@ Refer to the [documentation][certbot-docs-cmd-opt] for more info
2. On the Tools -> Options... menu, go to the Web UI tab.
3. In the "Server domains:" field put `yourwebuidomain.duckdns.org`
4. Tick the "Use HTTPS instead of HTTP" checkbox
5. a) If using version `4.2.0` or later:
5.
- If using version `4.2.0` or later:
- In the "Key:" text box paste the _path_ of the key file.
- In the "Certificate:" text box paste the _path_ of the certificate file.
- IMPORTANT NOTE: since the directory where these files usually are located (for example, `/etc/letsencrypt/live/yourwebuidomain.duckdns.org/`) is usually only readable by `root`, you may first need to copy the files somewhere that is readable by the user account that is running qBittorrent. Do not change the permissions of the original `certbot` directories.
5. b) If using older versions:
- **Important Note**: since the directory where these files are located (for example, `/etc/letsencrypt/live/yourwebuidomain.duckdns.org/`) is usually only readable by `root`, you may first need to copy the files somewhere that is readable by the user account that qBittorrent is running under. Do not change the permissions of the original `certbot` directories.
- If using older versions:
- In the "Key:" text box paste the _contents_ of the key file (for example, `/etc/letsencrypt/live/yourwebuidomain.duckdns.org/privkey.pem`). You may need root privileges to access this file.
- In the "Certificate:" text box paste the _contents_ of the certificate file (for example, `/etc/letsencrypt/live/yourwebuidomain.duckdns.org/fullchain.pem`). You may need root privileges to access this file.
6. Click save, close the tab and now you should only be able to access your Web UI via HTTPS.
# Automating certificate renewal