Replies: 2 comments 7 replies
-
I had the same issue. Adding the intermediate certificates to my reverse proxy resolves the problem. |
Beta Was this translation helpful? Give feedback.
0 replies
-
It's a 500 status code, I think flood can verify this tls cert but something else happened. OK I forget, this 500 is response code of flood server , not qb server |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Asking here as I'd rather not communicate through Discord;
I've done a fresh install on Armbian using the node repo and npm, with a 'download' user that is in the ssl-cert group, with a 'download' group writable run dir and a .service including SSL arguments (same LetsEncrypt certs that work on my qBitTorrent web on a different port), and I'm trying to connect to my qBitTorrent web install but I'm getting this in my log;
context;
I've also tried noauth and setting qt user, pass and address flags, and rebooted to be sure.
Might I have missed something here? Thanks for any advice.
Beta Was this translation helpful? Give feedback.
All reactions