Been using Sonarr for a while. Had an issues several months ago so didn’t update, but recently have been doing some overall updates on the server so went and upgraded it to the 2.0.0.4645 version. I also as part of those updates installed Radarr so I could familiarize myself with it and see about replacing Couch Potato. I had some login troubles with Radarr, but figured it’s still fairly beta-level at this point, so just disabled remote access to it and made it no authentication.
But now I’ve noticed that Sonarr is doing the same thing. I navigate to the IP/port for the computer (either localhost, on the LAN, or even remote IP) and it shows the login form like normal. I type my username/password, then the browser gives me an error saying HTTP error 500 and that it can’t process the request. In the url bar there’s the “returnto/” url but even if I type in a specific Sonarr page, it either gives me the login form again or the error page again. To make sure Radarr wasn’t conflicting (since I know it’s forked off Sonarr) I backed it up and uninstalled it completely (including the .config files and everything). I’ve disabled authentication in Sonarr for now and it works just fine, but this is not ideal since I’d like to have remote access as well.
Running on early 2009 Mac Mini, OSX 10.9.5, mono 4.0.1. Not sure what other info you need.
Ok, here is the debug log from an example. I tried to login a couple times after turning debug logs on (and restarted before the attempts, for good measure).
Not seeing any issues in the logs (I suspect that might be something not capturing that error properly on the server side that we need to look into).
Which browser are you using?
Have you tried another?
Are you able to open the develop console in your browser and see which request is throwing the 500 error?
Using Chrome (latest stable version on Windows 10) but I’ve tried Edge, the Chrome on my phone, and Safari on my Mac, and they all give the same error.
I am not super familiar with the develop console but I tried to use it and this is what it shows:
and it just shows a blank page or the 500 error page, depending on the browser.
I’m not sure if it’s related, but I noticed all my indexers fail their tests, as well. They all actually work just fine, for both automatic and manual searches, but when I do a test it shows them as failing. I captured a debug log from that incident (this actually happened to me once before, but I just rolled back my Sonarr to the previous version and it kept working fine. this is my first update since then, actually)
is the debug log with the failed index tests. I only tested three in there but it fails for all 9 that I’m using. (but does work just fine, only fails in the test)
I’m not super worried about the indexer fails because it does still work, just not sure if that’s related (it IS an older computer running an old OSX (10.9.5)
Thanks! I’m not seeing anything obvious and it seems to be working for me. We recently released an update to our develop branch that adds better logging around these 500 errors.
Definitely have cookies enabled, I usually have Sonarr and a few other sites keep me logged in. I’ve tried in my regular Chrome on Windows 10 and an incognito window, I’ve tried in Edge on the same PC, I tried in Chrome and Safari on the Mac that Sonarr is running on, and tried Chrome on my phone, all with the same result when I turn on form authentication.
I frequently disable authentication in order to fix this issue. I’ll change the config.xml, reboot the mac (so Sonarr restarts…no way to tell it to restart otherwise that I know of), it lets me right in. That’s how I’ve been using it, just had to disable remote access because now it has no password.
I do think it’s something wrong with the Mac, but I have a mono version Sonarr accepts (4.0.1), the program is up to date (still running that develop branch build you linked before, 2.0.0.4668). The OSX version is a little old at this point, 10.9.5, but it’s my understanding that the particular Mac mini model I’m using is not compatible with the next update. Haven’t looked into that in a while, as I have no reason to update, this machine just runs Plex/SABnzbd/Sonarr/CouchPotato and nothing else. I just have no idea what to do about this weird authentication error.
The reason I think it’s something to do with the Mac though is because of my original issue, which was the same thing happening with Radarr. I know it’s branched off some part of Sonarr’s code, but both programs having the same issue makes me think it’s the computer itself, just don’t know what. But I’ve uninstalled Radarr completely until I can get this figured out anyway, so not worried about that.
Thanks for the info, you should be able to restart Sonarr from the System page or even stopping the application in Resource Monitor (I think that’s what it is called) and restarting.
Updating Mono is probably worthwhile before blaming it all on the system, I don’t recall any specific issues with 4.0.1 but it could be disliking a change we made that has since been fixed. Worth a shot at least.