-
Notifications
You must be signed in to change notification settings - Fork 176
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
Post Processing Issues via Sonarr v4 - NZBDRONE: Server returned status 405 #1964
Comments
are there any sonarr logs generated at 2023-03-25 20:01:55 ? The 405 error indicates the url is not a valid method. So I wonder if sonarr no longer supports the api/command "DownloadedEpisodesScan" |
I've had a look at the Radarr logs, and I can see on the 5th line at 2023-03-25 20:01:55.5 what looks to be an error complaining that the Authorization header information was missing during authentication...
I've seen in previously raised issues on this github that there were changes made in the past that required additional header details to be included in the API calls, could this be similar? UPDATE 1 (25/02/2023): I just stumbled across this post while googling and although the post hasn't been answered, it appears that the line in the log file might be misleading. I noticed in Sonarr v4, they've enforced authentication during the first run wizard. However unlike Radarr v4 I am able to modifying the config.xml to There is a possibility that this is a "me problem" and I need to figure out how to configure the authentication method so that nzbToMedia is happy. UPDATE 2 (28/02/2023): I'm starting to think that this isn't necessarily a "me problem" after all. I have tried every auth option available in the GUI and the External method suggested in the docs, but having spent hours trying each method and then downloading a TV episode, they all show the same error in the logs (I'm paying more attention to the Sonarr logs this time too). The only potentially useful feedback from my troubleshooting is that I noticed that Sonarr have their authentication be mandatory whereas Radarr doesn't. Sonarr make you select a auth method and then provide a username and password, but Radarr allows you to select None therefore not asking for a username and password. I've no idea if that feedback is helpful but it's all I can conclude thus far. UPDATE 3 (02/04/2023): I spent some more time trying to get clarity on the authentication method and it seems that with my setup, the correct settings are to set I hope someone is willing to help work through this with me - I'm pretty convinced this is an issue between nzbToMedia trying to talk to Radarr v4 and how it deals with auth (which seems to be a lot more strict compared to a few of the other *arr services). I eagerly sit patiently hoping that this gets looked at, thanks. |
I started having issues as well. I think it began after upgrading Sonarr.
I think this where the problem lies
|
What version of Sonarr are you using @breezytm ? Your logs look different to mine. Your logs imply that the script is able to communicate with Radarr, which is where mine is failing. |
Sonarr version |
I just realized I misread your issue. It is regarding the beta version of Sonarr. Unrelated. I will open my own issue. |
Hi @clinton-hall et al, Where is/are the TV Show files saved before the post processing starts? My reason for asking is because the TV show begins downloading, gets to 100%, then unpacks successfully, but when the post processing fails, the files are deleted. Ideally for the time being I'd like to manually copy the TV show file(s) into their correct location and rename them manually. At least that way I can still get the TV Shows in a semi-automated way while further investigations can continue into why the PP script is not playing ball with Sonarr v4. Thanks. |
From memory the issue is (partly) because the URL for API access has changed in V4 Sonarr Edit the nzbToMedia file "nzbToMedia/core/auto_process/tv.py", and in the "elif section == 'NzbDrone':" section
These are lines 320 to 322 in the version of tv.py that I have It has been working for me for some time but I cant take credit for the solution, unfortunately I can't remember where I found it. |
@neil-bh from your logs, I can't see nzbToMedia deleting these files when the script fails... I would expect them to still be there. I have added the above mentioned fix into a new branch |
For info I then replaced the "master" branch with the "Sonarr-apiv3" branch and that works. |
I can also confirm that this is working when using the Sonarr-apiv3 branch. |
For credit purposes, I found the fix was discovered in this thread: #1908 (comment) |
@clinton-hall any chance that (until a PR is ready to be merged) that you could reference `Sonarr-apiv3' in the sidebar for this issue? |
Wow...I spent a lot of hours trying to figure this one out. I installed the V4 beta of Sonarr and had this issue...I don't know why my Google searches didn't show this earlier! Great work @clinton-hall , you always amaze me with this program. Works like a champ now. I assume at some point this would get merged in the master...but for now everything is working great! Thank you! |
now in master branch |
Describe the bug
I have upgraded my version of Sonarr to v4 which is the newest release which uses .NET instead of Mono. This lines up with Radarr v4. It looks great, but back on topic... After getting over the fact that I refreshed the API key for Sonarr and Radarr, I went back and updated any apps that used with the correct API key as well as updating the autoProcessMedia.cfg with the new API keys.
I now seem to be getting a 405 error when the post processing runs the nzbToMedia script. From the logs I can see that the TV show is downloaded successfully and unzipped etc. Then when the post processing starts I noticed a line in the logs that says:
nzbToMedia: [00:01:36] [WARNING]::MAIN: Connection to NzbDrone:TV failed! Check your configuration
then further on it says:
nzbToMedia: [00:01:37] [ERROR]::NZBDRONE: Server returned status 405
. I've enabled the logging options to get a more verbose output which I will paste below.Technical Specs
Expected behaviour
My expectations are that it would perform as it previously did so when using Sonarr v3. I'm not sure what the 405 error is representing, nor do I understand or know how to troubleshoot the fact that the script is claiming it has an issue talking to Sonarr/Nzbdrone. The log file also mentions
2023-03-25 20:21:22 INFO ::MAIN: NzbDrone:TV Could not create a fork object for default. Probably class not added yet.
which looks unusual. Do you have any ideas or pointers that can help?Note: It is worth pointing out that the post processing on Radarr downloads (using the Radarr script category 'Movies' is working fine).
Log
The text was updated successfully, but these errors were encountered: