Deluge v2.0b2.dev daemon.login timeout ... ?

[kslr]

>>> client = DelugeRPCClient('127.0.0.1', 58846, 'localclient', '')
>>> client.connect()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/deluge_client/client.py", line 60, in connect
    result = self.call('daemon.login', self.username, self.password)
  File "/usr/local/lib/python2.7/dist-packages/deluge_client/client.py", line 89, in call
    raise CallTimeoutException()
deluge_client.client.CallTimeoutException

Deluge-web Work is normal ... I look at the development of the current branch daemon.login part, can help me look at the problem?

[JohnDoee]

It seems like they added a requirement for client version when logging in. They also wanted to change the protocol a little and that might have come into effect now too.

I prepared for the potential protocol change in a commented out line here: https://github.com/JohnDoee/deluge-client/blob/develop/deluge_client/client.py#L81 Line 81 can be used INSTEAD of line 82

If you want to do a quick test for an easy fix, try changing https://github.com/JohnDoee/deluge-client/blob/develop/deluge_client/client.py#L60 to

        result = self.call('daemon.login', self.username, self.password, client_version='deluge-client')

Otherwise you'll have to wait for me to actually get Deluge 2 running and see how it works :smile:

[kslr]

Thank you for the information that I am trying to do with plugin solution. But that's a bad idea. The new RPC looks like a mandatory use of SSL...

[kslr]

I tried to replace two places and tested separately, but could not work.

[JohnDoee]

I apologize for not getting around to fix this, I forgot all about it.

Anyways, deluge 2 support has been added and is release - thanks for reporting the issue.