Action buttons won't respond (save, search, etc.)

Help & Support
1

Sonarr version (exact version): 2.0.0.4146
Mono version (if Sonarr is not running on Windows): 3.2.8
OS: Ubuntu 14.04.4 LTS
((Debug logs)) (posted to hastebin or similar): http://pastebin.com/0jn3KUsi
Description of issue:
When using Sonarr remotely (through an nginx proxy), I am no longer able to click action buttons like ‘save’ or ‘automatic search’. They just don’t respond. This started recently, though I’m not sure why. I haven’t changed any proxy settings, configuration changes in Sonarr, etc.

Sonarr works as intended when accessing it on my local network.

Troubleshooting steps taken:

  • restarted Ubuntu
  • ran system updates
  • verified proxy settings

Video of the issue here: https://drive.google.com/open?id=0B46_rmjiXepsUlFzX25kTkRVZWM

2

It sounds like nginx is dropping the request or the response, they are all POSTs or PUTs from the UI to the server. If you enable ((Debug logging)) (bypassing the reverse proxy since you can’t save), Sonarr will log requests to the API.

3

Here’s a debug log from after I tried editing a series and saving it, through the proxy.

http://pastebin.com/LcrCm2bJ

4

The logs only show GET requests, no POST or PUT requests, looks like the proxy isn’t passing them through.

5

That’s frustrating - my nginx config hasn’t changed at all, and Sonarr was working fine at first.

I’ve dug through a ton of forum posts/Google searches with no luck. Have you seen this issue before?

6

Pretty sure I have and if I recall correctly it was a bad nginx config, nothing else really explains it, since it works fine without the proxy I’m assuming (locally) and the logs don’t have the requests coming in at all.

Just saw this as well… you need to be running 3.10 or higher, anything lower will not work properly, though not this specific issue.

7

Thanks for catching that - I’m on 4.2 now. Not sure how I got to 3.2 using the Mono repository…

Anyways, I got it! Guess I’m an idiot - I had added the following to my nginx config based on a suggestion concerning security:

if ($request_method !~ ^(GET|HEAD|POST)$ ) { return 405; }

I added ‘PUT’ into that and we’re good to go.

Thanks for taking a look at it, either way! :sweat_smile:

8

Http verb OPTIONS and more importantly DELETE.

9

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