Put.IO client broken
Before submitting your issue:
Enable debug logging from settings in SiCKRAGE then try and reproduce the error
Put.io client is not working (Cannot authenticate). Adding an extra log entry to log this exception shows that the problem is the response from the authentication here does not contain a "location" header (as expected here)
Steps to reproduce
Configure a put.io account and do "Test Connection". Add a log entry to capture this exception
What is the current bug behavior?
The UI says "Error: Unable to get putio Authentication, check your config!"
What is the expected correct behavior?
The test is performed correctly, and the client can be used.
Relevant logs and/or screenshots
This log entry is a result of adding an extra log (as mentioned above), this log entry won't show up on the logs otherwise.
2018-12-15 22:28:25 ERROR::CORE::Error while authenticating with put.io: u'location' Traceback (most recent call last): File "/volume1/@appstore/sickbeard-custom/var/SickBeard/sickrage/clients/putio.py", line 54, in _get_auth response = self.session.get(response.headers['location'], File "/volume1/@appstore/sickbeard-custom/env/lib/python2.7/site-packages/requests/structures.py", line 52, in __getitem__ return self._store[key.lower()] KeyError: u'location'
I'm assuming there have been breaking changes on the put.io API. It seems that the API uses plain OAuth with an authorization code grant, but the code seems to be using a special type of grant that may have been deprecated.