-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
as of Pre-release v0.8.10 - 401.Unauthorized #1654
Comments
Thanks for testing the pre-release and reporting @PaintPauller 2nd issue: Do you get the same thing if visiting http://127.0.0.1:9117/torznab/thepiratebay/api?t=caps&apikey=YOUR_API_KEY in your web brower Can you post the full Jackett logs ie I've tested here and it works for me |
i can confirm that the api key is correct in sonarr and http://127.0.0.1:9117/torznab/thepiratebay/api?t=caps&apikey=YOUR_API_KEY does work for me so i have no idea whats going on. as for the logs nothing shows up in the normal log and i am unable to turn on Enhanced logging because of the settings bug. where would i put in the above command? sorry im somewhat new to all of this. |
v0.8.12 should fix the settings issue Thats strange that it works in the browser |
windows |
update version to latest |
here is the enhanced logging when I hit test in sonarr
|
log.txt |
Can you remove KickAssTorrent from both Jackett and Sonarr to see if thats the cause of the issue? |
i have already removed KickAssTorrent from both unless you are talking about KickAssTorrent (kat.how). |
removed KickAssTorrent (kat.how) from both jackett and sonarr. no change, every index still gives 401 in sonarr. |
completely reinstalled jackett Version 0.8.12.0 and deleted all my jackett indexers from sonarr. still get the error "Unable to connect to indexer, check the log for more details" has the API Path changed from /api or any ideas? with this error you cant even hit the save button in sonarr. |
the logs should have more information... Stop Jackett Otherwise, if not interested in getting your hands dirty, go back to the last released version v0.7.1644 |
@PaintPauller could you turn on Debug level logging in Sonarr and upload your logs? Thanks. |
Same issue here for the past few days, just updated to 0.8.18 and still the same. Ran logs with the requested -t -l from above, here was the result
|
@D4rk56 please post your enhanced Jackett logs as well |
|
just got up and updated to Jackett Version 0.8.25.0. everything looks to be working again! thanks for all the help! |
i'm on 0.8.25.0 and i'm still getting the error for both torznab and potato feed |
ok take that back i was able to reproduce the problem but i may have narrowed it down for you. after i got all 10 of my indexers set up and working i went to add a Admin password to jackett and as soon as i did that sonarr stopped working and started producing the 401.Unauthorized hope this helps you track it down! |
just changed my password back to blank and it still does not work so i think it has something to do with a fresh install. i say this because before you make a password shows as "blank to disable" but when you add a password it changes to **** and even after changing it back to blank it shows as **** and will still produce the 401.Unauthorized error in sonarr |
@PaintPauller that's actually very helpful, and I hope I've finally found the issue. v0.8.26 should resolve it, please give it a go. |
i can confirm that v0.8.26 fixed it. even after adding back a password sonarr no longer gives the 401.Unauthorized error. thanks for the fix and glad i was able to help you out! |
It works for me, but only for Radar, not Sonarr. |
Same issue as D4rk56, some don't work in Sonarr while they do work in Radarr. I have a few that do work in Sonarr but the majority don't. |
400.BadRequest
|
Torznab routes work for me within Sonarr now. Potatofeed routes return a |
Just to confirm I still get this error as well 401. |
also get failed test in sonarr on eztv, sky torrents, torrent project, but the pirate bay works i am on windows Jackett Version 0.8.48.0 i was getinging the 401 error now i am geting and <Error><Message>skytorrents does not support the requested query.</Message></Error>```
i have to manually set Categories in sonarr to match the ones in jackett
i did not have to do this befor is this intended ?
if so the "Adding a Jackett indexer in Sonarr or Radarr" needs updating
|
Everyone getting HTTP error 400 and "xyz does not support the requested query", v0.8.49 probably fixes that. Please update and see if it's working. |
Fix v0.8.49 work for me ! |
Jackett Version 0.8.55.0 all fixed for me |
i have the error on latest pre-realse version 0.8.67.0 |
@KennyVB that looks like its not passing the user and its doing user and the key twice |
I cannot wrap my head around why it has started to fail now as it was faulty from the beginning... Anyway, SupportsCategories didn't really take sub categories into account, which is bad. - Potentially fixes Jackett#1654 and Jackett#1656
as of Pre-release v0.8.10 i am unable to change any settings in Jackett for some reason but more importantly sonarr is unable to connect with jackett. i keep on getting this in sonarr:
Unable to connect to indexer, check the log for more details
Log: 17-8-11 17:15:12.5|Warn|HttpClient|HTTP Error - Res: [GET] http://127.0.0.1:9117/torznab/thepiratebay/api?t=caps&apikey=(removed) 401.Unauthorized
Jackett version: v0.8.10
Mono version (if not using Windows):
The text was updated successfully, but these errors were encountered: