Opened 5 years ago
Last modified 5 years ago
#3283 new bug
Authentication Failure
| Reported by: | CaryV | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | needs verified |
| Component: | Unknown | Version: | 2.0.3 |
| Keywords: | Cc: |
Description
Since upgrade to 2.0.3, clients are no longer able to connect / use Deluge - gives an "Authentication Failure" on the Password that is entered. It had always worked before (with a blank password). Assigning a password makes no difference. (see attachment for view of failure, pertains to Radarr specifically - as soon as a link is found to attach) Since Deluge was the ONLY upgrade that took place, there is no doubt that the problem rests with a change made to Deluge AND it is still working fine on another machine where Deluge was not upgraded (from v1.3.15)
Attachments (4)
Change History (7)
by , 5 years ago
| Attachment: | Deluge_log.txt added |
|---|
by , 5 years ago
| Attachment: | Deluge_log.2.txt added |
|---|
by , 5 years ago
| Attachment: | Deluge_log.3.txt added |
|---|
by , 5 years ago
| Attachment: | Deluge_Failure (1).zip added |
|---|
comment:1 by , 5 years ago
Web-site should notify when attachment has been successfully uploaded... .2 and .3 are dupes (with NO removal capability)
comment:3 by , 5 years ago
As of most recent update of (binhex-) Radarr from v0.2.0.1344 to v0.2.0.1358, Password is once again validating to allow access (use of) Deluge v2.0.3 Interestingly enough, as mentioned, Deluge v1.3.15 worked (on both systems) and is [still] working fine (on the another system) with Radarr v0.2.0.1344. It did not become dysfunctional until upgrade of Deluge to v2.0.3 and since it now validates and works since Radarr's [most recent] update, something obviously became 'disjointed' between the two. Problem has been verified as outlined in this submission and is now resolved. Ticket can be closed.
Log file