New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deluge 2 Beta Authentication Support #2412

Open
danielloader opened this Issue Feb 14, 2018 · 4 comments

Comments

Projects
None yet
5 participants
@danielloader

danielloader commented Feb 14, 2018

Support / Questions

Please use https://forums.sonarr.tv/ for support. Support requests or questions will be redirected to the forums and the issue will be closed.

Bug Report

System Information/Logs

Sonarr Version:
2.0.0.5085

Operating System:
Ubuntu Server 16.04.3 LTS

.net Framework (Windows) or mono (macOS/Linux) Version:
Mono 4.2.1

Link to Log Files (debug or trace):

18-2-14 16:43:36.5|Error|Deluge|Unknown method

[v2.0.0.5085] NzbDrone.Core.Download.Clients.DownloadClientAuthenticationException: Unknown method
  at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.ProcessRequest[TResult] (NzbDrone.Core.Download.Clients.Deluge.DelugeSettings settings, System.String method, System.Object[] arguments) <0x40fb7680 + 0x0019f> in <filename unknown>:0 
  at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.GetVersion (NzbDrone.Core.Download.Clients.Deluge.DelugeSettings settings) <0x40fb7620 + 0x00047> in <filename unknown>:0 
  at NzbDrone.Core.Download.Clients.Deluge.Deluge.TestConnection () <0x40fb6f70 + 0x000a0> in <filename unknown>:0 

18-2-14 16:43:36.5|Warn|NzbDroneErrorPipeline|Invalid request Validation failed: 
 -- Authentication failed

Browser (for UI bugs):
Chrome Latest

Additional Information

Deluge 2.0.0.dev7125

Feature Request

What problem are you looking to solve?

Be able to pass the test in the download client modal.

Other Information

I think it's actually working and passes torrents correctly, just throws an error here.

@Subcode

This comment has been minimized.

Show comment
Hide comment
@Subcode

Subcode Apr 25, 2018

Having the same issue.
Sonarr: 2.0.0.5169
Deluge: Deluge 2.0.0.dev7126

Subcode commented Apr 25, 2018

Having the same issue.
Sonarr: 2.0.0.5169
Deluge: Deluge 2.0.0.dev7126

@cocokola

This comment has been minimized.

Show comment
Hide comment
@cocokola

cocokola Apr 29, 2018

Having the same issue
Sonarr: 2.0.0.5163
Deluge : 2.0.0.Dev7126
windows 7

cocokola commented Apr 29, 2018

Having the same issue
Sonarr: 2.0.0.5163
Deluge : 2.0.0.Dev7126
windows 7

@BoKKeR

This comment has been minimized.

Show comment
Hide comment
@BoKKeR

BoKKeR May 3, 2018

I can take a look at this. The login seems to be going through.

5:06:30 [DEBUG ][deluge.ui.web.auth :61 ] Received a password via the 1.2 auth method 15:06:30 [INFO ][deluge.ui.web.auth :65 ] Login success (ClientIP 127.0.0.1) 15:06:30 [DEBUG ][deluge.ui.web.auth :61 ] Creating session for admin

BoKKeR commented May 3, 2018

I can take a look at this. The login seems to be going through.

5:06:30 [DEBUG ][deluge.ui.web.auth :61 ] Received a password via the 1.2 auth method 15:06:30 [INFO ][deluge.ui.web.auth :65 ] Login success (ClientIP 127.0.0.1) 15:06:30 [DEBUG ][deluge.ui.web.auth :61 ] Creating session for admin

@BoKKeR

This comment has been minimized.

Show comment
Hide comment
@BoKKeR

BoKKeR May 3, 2018

The problem is with the daemon.info method. As of right now, it seems to be missing from the new deluge release. As it returns
"message": "Unknown method",
While the old 1.3.11 returned the version number in the json
"result": "1.3.11",
I think the best we can do is contact the developer and ask about it. I am sure it will be added sooner or later. There is no problem with the authentication and the rest of the API seems to be working too.

BoKKeR commented May 3, 2018

The problem is with the daemon.info method. As of right now, it seems to be missing from the new deluge release. As it returns
"message": "Unknown method",
While the old 1.3.11 returned the version number in the json
"result": "1.3.11",
I think the best we can do is contact the developer and ask about it. I am sure it will be added sooner or later. There is no problem with the authentication and the rest of the API seems to be working too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment