#11
Something you may try is log in to deluge from your web browser and then try again in the app
What was the line you added? As I need to do this to mine.mitsuhide wrote:mediacowboy hits on a good point. Depending on how your Deluge is set up, it won't be 'active' upon startup unless you log in once and start the daemon. At least this is how it operates with my docker setup. I ended up adding a line to the core.conf to automatically connect to the default daemon on startup which fixed this.
Otherwise, I have it working fine via reverse proxy.
My primary connection address is set as such:
http://user:password@mydomain.com/deluge
deluge web password is set appropriately.
going to https://mydomain.com/deluge works fine after it presents me with the basic auth request.