Cannot Login to Web ThinClient

[vinbullet]

Hello, running 64-bit Pi OS Lite, and allowed all incoming connections from local network. I am having trouble getting logged into the daemon through the WebUI, after following both the https://deluge.readthedocs.io/en/latest ... rvice.html and the https://dev.deluge-torrent.org/wiki/Use ... ThinClient

I was pretty sure deluged was using the configs from

Code: Select all

/var/lib/deluge/.config/deluge/

but I have also been mirroring changes to

Code: Select all

~/.config/deluge/

I replaced the localclient line in the home dir auth file with the one in /var as well.

After changing allow-remote to true in both configs, and adding my login with account type 10, I am still unable to connect through the web-UI on my regular computer. I haven't changed any of the settings besides download dir and max seeding/downloading/active torrents in the config.

Both services show up as running on ssh, and I can load and login to the WebUI, but not to the daemon in connection manager. There's nothing in either log file besides an error "no translation file" in web.log. I am a bit stumped as to what to try next. I'm starting to see why I went with a GUI program over VNC last time I tried this setup lol.

[ambipro]

Just to confirm, you are trying to connect with the thinclient (over daemon) on the webui port? or you can't connect to the WebUI (using browser) or via the thinclient (via daemon port)? You need to use the appopriate port...Found in the "Daemons" section of preferences. WebUI is strictly for the web interface if i'm not mistaken, and thinclient utilizes the daemon port, not needing the WebUI plugin at all. I use standalone, though, so I could be mistaken.

I'm also confused as you say you're having trouble logging into the daemon through the WebUI, then say you can load and login to the WebUI but not the daemon, if you could clarify, use terms like "using thinclient" or "using WebUI" rather than ambiguously switching between or using both, that would help clarify.

Also, you could try using a SSH Tunnel and seeing if it works when connecting via localhost, that would clarify if it's a configuration problem in deluge, or a firewall/network issue.

For future reference, the command line for a specific directory for config/profile/data is "-c \path\directory\here" and logs are "-l \path\logfile" if you're trying to figure all this out. I'd also recommend running in debug mode when you log, just to see what all is going on.