Release/push stopped working after update

Sonarr version (exact version): 2.0.0.4855
Mono version (if Sonarr is not running on Windows): 5.0.1.1
OS: debian
Description of issue:
I have a script in python that listens to an irc announce feed and relays them to sonarr via the release/push api. Up until the july 4th update (2.0.0.4855) it had been working flawlessly. My log goes from contant release/push calls on july 3rd to nothing on july 4th. So i believe I have narrowed the issue down to a change new to that version. The script does a basic python requests POST with api-key in the header and json parameters in the body. So where I think I am running into an issue is that I have omitted the base url for my api sonarr address ie. http://localhost:8989/api/release/push. This was working prior to the update. Now it returns {‘message’:‘not found’}. It does however redirect to http://localhost:8989/sonarr/api/release/push as expected but does not seem to communate with the api anymore. It is also interesting that http://localhost:8989/api/system/status and http://localhost:8989/api/release both work in the newest version so it appears to be isolated to release/push. While I don’t full understand this commit (https://github.com/Sonarr/Sonarr/commit/de5ce239893e0698e85228cb5648351f18bfbbbd) is it possible that it has somehow messed up the release/push module when the baseurl is not included?

If you have a base URL, then yes, because the request would be redirected and POSTs don’t follow redirects in the same way a GET request does.

I am having the same issue with a script that I wrote as well.

All my other API calls for Series, Episodes, and Releases work fine. But when I want to POST and request a Release to download, it returns the same: {‘message’:‘NotFound’}

I am not seeing the redirect you mentioned and I do not think that I have a “Base URL” issue, but maybe I am missing something.

Oddly enough if I try either api/release or api/system/status with POST instead of GET it still works fine. It seems to be specific to the release/push module. I was able to correct my issue by changing http://localhost:8989/api/release/push to http://localhost:8989/sonarr/api/release/push. It does seem rather odd that the release/push module is the only one affected the change.

Edit: ‘/sonarr’ is entered in the ‘URL Base’ field under general settings in my setup

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