Page 1 of 2

Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Wed Jul 05, 2017 2:14 pm
by AdmirableAvalanche
A week ago, I setup sabnzbd, sonarr, and radarr both locally and remote with reverse proxy. All three seemed to be working fine. Now, today all of a sudden, radarr and sonarr give an "error: null" response, but sabnzbd still works fine.

In a web browser, I can still access all three applications remotely and locally without issue. But on nzb360, only sabnzbd connects. Radarr/sonarr cannot connect locally or remotely.

How do I even begin to troubleshoot something as vague as "error:null" ? Nothing changed in sonarr/radarr with ports, settings, credentials, or APIs. Nothing shows up in the logs of sonarr/radarr. Nothing shows up in my web server logs for reverse proxy issues. And I don't see anywhere on the app that provides a log with more information.

Any ideas?

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Wed Jul 05, 2017 3:44 pm
by Kev
Null is coming back from those services in terms of an error. This is usually because it cannot connect to the server instance. Is your API key correct?

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Sat Jul 08, 2017 1:11 pm
by AdmirableAvalanche
Kev wrote:Null is coming back from those services in terms of an error. This is usually because it cannot connect to the server instance. Is your API key correct?
Unless API keys somehow have the ability to modify themselves on their own, yes, the API key is correct. Nothing has been modified on the phone app or the services.

I double checked the API anyways and they're for correct.

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Tue Jul 11, 2017 6:22 pm
by AdmirableAvalanche
...so no further ideas then?

And seriously no logs? No way to breakdown what "error:null" means, exactly?

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Tue Jul 11, 2017 8:15 pm
by f3bruary
Is there anything in the server logs ? When checking, make sure debug logging is switched on.

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Tue Jul 11, 2017 9:03 pm
by Kev
I need to add better logging, no doubt. Since you're using reverse proxies, my bet is how you entered in the details into nzb360. Can you send me a PM with your settings page?

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Mon Aug 07, 2017 7:02 am
by JAS
Hey Kevin,

I've also been getting this error on sonarr recently when trying to add new episodes. "Error:null". I was just wondering if there was a fix for it yet? I have the correct API key and the host name and settings are correct. I'm able to load my sonarr just fine on chrome so that's all working fine. I even double checked my nzb get settings and that's all correct.

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Tue Aug 08, 2017 3:02 am
by Kev
Are you on the development channel for updates?

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Tue Aug 08, 2017 3:14 am
by AdmirableAvalanche
Kev wrote:Are you on the development channel for updates?
I'm not now, but I'd be happy to switch if you need me to help test changes to the connectivity settings.

Sent from my SM-G950U using Tapatalk

Re: Error:Null - How Do I Even Begin To Troubleshoot That?

Posted: Wed Aug 09, 2017 3:31 am
by Kev
Nah, stay on stable if you want the most stability with nzb360. Which show are you trying to add?