Open BaukeZwart opened 1 year ago
If I'm not mistaken, this is something that could be easily accomplished with a reverse proxy setup such as nginx, swag or caddy (just two popular options of many choices)
nginx in my case
nginx in my case
https://shairosenfeld.blogspot.com/search?q=nginx would seem relevant perhaps, just a quick search.
I was hoping for a fix where I don't have to mess with NGINX on the seedbox, managed that for all other apps, CS is the only one that I haven't managed to get https working for. I'm terrified to lock myself out. And that won't be a solution for users on a shared box, they won't have root access and probably can't access the NGINX settings.
I was hoping for a fix where I don't have to mess with NGINX on the seedbox, managed that for all other apps, CS is the only one that I haven't managed to get https working for. I'm terrified to lock myself out. And that won't be a solution for users on a shared box, they won't have root access and probably can't access the NGINX settings.
Did you ever get this to work? I am having the exact same problem
I run CS on my local host and qbit on a remote seedbox that requires proxy authentication when accessing via https. When I ty to set the qbit url in the config to https://user:pass@domain/qbittorrent I'm getting a qbit login error.
qBittorrent login failed with code 401
Would it be possible to support proxy authentication so https can be used when accessing remote clients?