Deluge Console Issues - For the attn of mhertz

[phoenix1of1]

Hi mhertz,
I noticed you have answered about the same/similar issue on viewtopic.php?p=237574#p237574
Just wanted to touch base as I am experiencing either something very similar or the same issue whereby deluge-console does not work.

I have a trace log here - https://privatebin.net/?91a21b72cc5aa29 ... X49biJq8GQ showing a TypeError.

I talked to Ambipro who suggested trying dev build 127 but was still seeing the same TypeError so was nosing around and stumbled on the above thread and so have proceeded to implement as per the instructions on the thread.
Noted and confirmed that the TUI for deluge-console is still in dev and otherwise frozen.

Tried the following command:

Code: Select all

deluge-console.exe --daemon deluge --port 58846 --username <your username> --password <your pword> info

The use of "info" isn't recognised and comes up as an invalid argument so running the same command without "info" results in the TypeError available in the tracelog.

Without trying to sound like a prat, the console issue stops me using a custom script to stop/start added torrents until traffic is received.
Why do this - Because when a torrent is added to Deluge via Autobrr, the torrent fails to start any traffic flow for anything up to 5 minutes+ so I am losing ratio. Found a thread on reddit that suggested stop/starting until the traffic was received which then bypasses the need to re-announce to a tracker every second which is generally frowned upon by trackers and so that led me on to the custom batch script which needs to make use of the deluge-console to accomplish this.

I did note that the other user on the thread above had success where as I haven't so the question we have to ask is why?

On that note, here are the rig details:
Win11
Latest stable Deluge 2.x.x (Have tested 2.x.x dev build 127)
Running Deluge in Thin Client mode
Deluge is installed locally
ltconfig set for racing

Got a half decent build with a gigabit network connection so want to utilise it to full effect which is why I am chomping at the bit to get the script up and running with deluge-console otherwise I'm close to back of the swarm feeding everyone else's ratio.

Any light you could potentially shed on this would be greatly appreciated and warmly received.

Please don't hesitate to reach out if you need more from my end.


Thank you
Kind Regards

phoenix1of1

[mhertz]

Sorry, just catched up here, and seen... You/others can PM me if wanting something from me specifically, but anyway, indeed you're right in that it is same issue, and solution same, which I just again reconfirmed working. There's a PR open for this btw, so hopefully will be fixed in dev branch soon, but is a workaround, rather than actual fix, so maybe Cas prefers wait until he can figure out an actual true fix, not sure, but meanwhile the instructions in your linked post work i.e. download and unzip the link I provided, into location I referenced, and will work again. As said, the TUI(curses UI) never worked on windows, and also now in dev branch states that specifically to you(while TUI blocked), and currently will just freeze as you report.

With that fix applied referenced above, there's still another issue, which I have been to lazy report ticket about yet, and only briefly looked into and first thought being i'm not good enough to fix, but well see - anyway, it's about when using chained 'connect' commands, so e.g. 'deluge-console connect <host:[port]> <user> <pass>'; info', then errors out, because of a previous commit I narrowed it down too, and so I found can workaround by using said -'U,-P,-d,-p' switches instead, so e.g. then would instead become: 'deluge-console -d <host> -p <port> -U <user> -P <pass>'; info'.

Hope helps, and sorry missed it, didn't blow you off on purpose.

[phoenix1of1]

Hey mhertz,
No worries, you and the rest of the team do this off your own backs so waiting a day or two for a response is no big deal in my books and I didn't want to presume by PMing you directly.

Can confirm I was just being a pillock, for future reference for anyone else that comes across the issue before a fix is implemented, here's the full run-down of actions you need to take:


Linux instructions will differ a little, I'm an evil Windows user *queue maniacal laughing/cackling*.

1) Get the console.zip from - https://onedrive.live.com/?authkey=%21A ... by&o=OneUp

2) Go to your Deluge install directory, for example "C:\Deluge

3) Find the sub-folder called "Deluge" then enter the folder called "UI".

4) Unzip the file you downloaded earlier and drop it in to the location in step 3, it's a folder called "Console". You will now have a "Console" folder in your "UI" folder.

5) Open up a terminal in your Deluge install directory - this is the place where the deluge-console lives.

6) Open up your hosts file by navigating to "C:\Windows\System32\drivers\etc" and edit the host with a text editor in admin mode, add <IP Address> <deluge>
For example, if you run Deluge and Deluged daemon on the same machine, set an entry in the hosts file to - 127.0.0.1 deluge, save then close.

7) Use the following command - deluge-console.exe -d <host> -p <port> -U <user> -P <pass> help
Host = IP address of where deluged daemon is running, if it's on the same machine as Deluge, use 127.0.0.1.
Port = your deluged daemon port. Default is 58846.
User = User name set in Preferences tab under Daemon. Default username is - localhost
Pass = Password set for the user. If you are not sure of the password, go to "C:\Users\<your user account>\AppData\Roaming\deluge" and open up the file named "auth" in a text editor, this will display the username, password and access level. All you need is the password.

The help command will give you the overview on all other available commands to run.

Where did I go wrong? I didn't set the host file to point to Deluge on my localhost and I didn't use the correct flags, it has to be the shorthand flags and just an FYI, they are case sensitive. I used the expanded flags.

As the rule says, 99% of issues a user encounters is user error with 1% being an actual issue/bug...I just so happened to prove that rule and hopefully help a few people avoid proving that rule too.
----------------------------------------------------------------------------------------------------

mhertz - Appreciate the feedback and the information and the effort you all put in to Deluge!

PS: Don't worry, I don't hold a grudge for long...only a decade or two

[mhertz]

Thanks for the kind words buddy, and helpful writeup

Just wanted to reiterate that the zip is the full fix, and only needs the '-d,-p,-U,-P' switches if specifically running 'connect' semicolon'ed with other commands, in which case should be changed to that(instead of 'connect'), otherwise not needed(localhost connect automatically by deluge). The host file change shouldn't be needed, at-least never personally had to.

Thanks as said bud.