Does WebUI/KeyPath | WebUI/CertificatePath actually accept file paths?

[TDuffinNTU]

Using LetsEncrypt/Certbot I've used dietpi to set up my server's SSL certs, which are kept in /etc/letsencrypt/live/DOMAIN/cert.pem and privateKey.pem respectively. Since the certs may update they're

In qBittorrent.conf the lines that store the cert are WebUI/KeyPath and WebUI/CertificatePath but when I use the path to the cert/key in these variables the web UI doesn't load at all.

I can't find any documentation of the WebUI-specific settings for qbittorrent (the git repo just links to a page unrelated to them) so I'm wondering if anyone else knows what exactly I should be putting in here?

[TDuffinNTU]

Yup, it's the path, but only root can read /etc/ so they need to be copied with a hook script. thanks me!

Link: https://github.com/qbittorrent/qBittorrent/wiki/Linux-WebUI-setting-up-HTTPS-with-Let's-Encrypt-certificates

EXTRA NOTE: chown qbittorrent cert.pem && chown qbittorrent privateKey.pem after moving the files to a suitable place or you'll still be stuck.

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.