Started getting Deluge Authentication Error

Help & Support
1

Sonarr version (exact version): 2.0.0.3953 - Mar 12 2016
Mono version (if Sonarr is not running on Windows): not sure
OS: CentOS 6.5
((Debug logs)) (posted to hastebin or similar): http://pastebin.com/HuHuYcPg
Description of issue (if you think you’ve found a bug please include steps to reproduce):

I have been using deluge 1.3.12 for a while now with no issues but i went on my server, noticed it had updated the the latest sonarr version and that downloads weren’t being started, after investigating i found that the deluge download client said it couldn’t authenticate, i checked the password worked with deluge which it did and re-entered it into sonarr but still got the same message. i have also removed the deluge download client from sonarr and attempted it again, with no joy.

2

We’ll need to see ((trace logs)) of the issue (the logs you posted are only error logs).

3

Hi Sorry,

http://pastebin.com/khHBNthD

this should show the auth issue

4 
16-4-6 10:04:23.1|Debug|DelugeProxy|Url: http://192.168.10.18:8112/json Action: daemon.info
16-4-6 10:04:23.4|Debug|RestSharpExtensions|Validating Responses from [POST] [http://192.168.10.18:8112/json] status: [OK]
16-4-6 10:04:23.4|Trace|RestSharpExtensions|Response: {"id": 39, "result": null, "error": {"message": "Not authenticated", "code": 1}}
16-4-6 10:04:23.4|Debug|DelugeProxy|Url: http://192.168.10.18:8112/json Action: auth.login
16-4-6 10:04:23.5|Debug|RestSharpExtensions|Validating Responses from [POST] [http://192.168.10.18:8112/json] status: [OK]
16-4-6 10:04:23.5|Trace|RestSharpExtensions|Response: {"id": 40, "result": true, "error": null}
16-4-6 10:04:23.5|Debug|DelugeProxy|Deluge authentication succeeded.
16-4-6 10:04:23.5|Debug|DelugeProxy|Url: http://192.168.10.18:8112/json Action: web.connected
16-4-6 10:04:23.7|Debug|RestSharpExtensions|Validating Responses from [POST] [http://192.168.10.18:8112/json] status: [OK]
16-4-6 10:04:23.7|Trace|RestSharpExtensions|Response: {"id": 41, "result": null, "error": {"message": "Not authenticated", "code": 1}}

Sonarr authenticates successfully as shown on lines 4-7, then immediately gets rejected on the next request. I checked and we’re not communicating any differently with Deluge in 2.0.0.3953. Perhaps there is something in Deluge’s logs that explains why its failing.

5

Thanks for the reply, I have looked at the deluge logs and all i see is this:

http://pastebin.com/WMZ4Asxt

i have replaced my password with MYPASSWORDHERE

7

Deluge’s logs only seem to indicate that it successfully connected, but nothing about why it rejected the connection. I’m not sure what it could cause that.

Looking at the log and the code, the first request gets rejected because its not authenticated so Sonarr authenticates, then the request fails again because its not authenticated so Sonarr gives up. Unless Sonarr isn’t setting the auth cookie correctly I don’t see how it could fail, but if that was the case it wouldn’t ever work.

8

So frustrating I have no idea what is going on and why it’s not working. I’ve been using this version of deluge and it used to work fine. Only thing that changed was somarrr :frowning:

9

If you can, try the develop release, there are some general communication changes that affect all clients, be good to know if there is any change.

1 Like
10

I’ll try that tomorrow and let you know how it goes :slight_smile:

11

ok so upgrading to the develop branch resolved the issue :slight_smile:

1 Like
12

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.