New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option for TLS keys and certificate to be a file path #7547

Open
C0rn3j opened this Issue Oct 5, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@C0rn3j

C0rn3j commented Oct 5, 2017

qBittorrent version and Operating System:

3.3.16, Arch Linux

What is the problem:

image

There is no way to specify a file path instead of the actual key. I use Let's Encrypt for the certificates - I do not want to go to qbit settings every 90 days. I just want to set the path to the live LE folder.

What is the expected behavior:

Can enter file path to the certificates. Certificates will be loaded from the file path.

@FranciscoPombal

This comment has been minimized.

Show comment
Hide comment
@FranciscoPombal

FranciscoPombal Jan 23, 2018

Contributor

@C0rn3j I just finished writing a Wiki page that might help you:
https://github.com/qbittorrent/qBittorrent/wiki/Linux-Web-UI-setting-up-HTTPS-with-Let's-Encrypt-certificates
Check the "Automating certificate renewal" section

Contributor

FranciscoPombal commented Jan 23, 2018

@C0rn3j I just finished writing a Wiki page that might help you:
https://github.com/qbittorrent/qBittorrent/wiki/Linux-Web-UI-setting-up-HTTPS-with-Let's-Encrypt-certificates
Check the "Automating certificate renewal" section

@C0rn3j

This comment has been minimized.

Show comment
Hide comment
@C0rn3j

C0rn3j Jan 23, 2018

Sadly it doesn't, I already knew how to automate obtaining certificates, and I'd still need to go to qbit settings every 90 days.

C0rn3j commented Jan 23, 2018

Sadly it doesn't, I already knew how to automate obtaining certificates, and I'd still need to go to qbit settings every 90 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment