New 2.1.1 install unable to run deluge-console

[pronator]

I just upgraded by deluge container from 1.3.15 to 2.1.1, and the web UI is working great. The Windows think client is working mostly great. But I can't figure out how to start deluge-console.

I used to do this after running sh in the container:

Code: Select all

deluge-console
connect :58846 USER PASS

But now I type deluge-console and I get this "Select Host" box.
* I did not add the host 127.0.0.1
* 'D' says it will delete the host but does nothing
* 'h' also does nothing
* Pressing Enter says "Password does not match", but it did not ask me for a password.

I did try

Code: Select all

deluge-console -u USER -p PASS

and it behaves the same.

I tried adding a new host but that gives me

Code: Select all

127.0.0.1: Invalid port. Must be an integer

. Of course I entered "58846".

Where does this username and password come from? I would assume /config/auth, because that's where the thin client passwords are.

[ambipro]

viewtopic.php?t=56846 Might be helpful

[pronator]

@ambipro Thank you, I'm using an Alpine Linux container, not Windows, but that post was helpful. Giving the command on the command line works, mostly. The interactive curses UI is broken for sure.

[mhertz]

Sorry slow, but would just add that the good DjLegolas fixed the "port not integer" issue, "host not deleting" issue, and "need esc to exit add-new-host dialog" issue, so will be in next deluge version.

Meanwhile, if wanted can all be applied locally to deluge 2.1.1 with:

Code: Select all

sudo find /usr -path '*/deluge/ui' -exec sh -c 'curl https://patch-diff.githubusercontent.com/raw/deluge-torrent/deluge/pull/393.patch | patch -d {} -p3 --no-backup-if-mismatch' \;

Regarding some other comments, then the -U and -P args isn't for curses mode but cli commands(instead of 'connect' command).

Initial host in curses UI is the 'localclient' one, which will say "password don't match" when trying connect when running under other user than deluged(e.g. deluge user and own user, mismatching). If not wanting make new user, then can e.g. also run as deluge user(sudo -u deluge deluge-console) or use -c arg and point to dir of deluge profile of daemon, often /var/lib/deluge/.config/deluge etc - though need sudo for access rights to said profile.

Hope helps.