SABnzbd Forums

Hi peeps!

I recently reinstalled SABnzbd on my Synology NAS, everything went ok. The only thing that bothers me is that i get warnings all the time:
I use third party programs on my cellhone (iPhone Safari) and on my home computer (Mac OSX 10.8, Chrome) but that's it. So someone must have my API key, login details and had my SABnzbd set in their 3rd party app. This kinda bothers me.

Since I don't use Firefox in the first place (which this person seems to use) and Mac OSX 10.7 i'm pretty sure it's not me. Also my office pc where I access SABnzbd once and a while has Windows 7, Chrome. So the identifier doesn't match with anything I own.

Is there some way to get behind the IP adress? I don't see anything in the logs so I'm guessing this is a NO.
Maybe using Synology software?

Thanks in advance guys, any help would be greatly appreciated!

UPDATE: I've installed the 'Darkstat' Synology package (network statistics analyzer). Can't access it from my current location but my hopes are that this tool could show me some addresses.

The warning should also show the IP address where the API call is coming from.
At least it does for recent versions (0.7.6+).

I'm using 0.7.7 but I'm only seeing this:

Move to 0.7.9, that should contain the IP.
Otherwise look at the log file on the Status page.

Installed 0.7.9, looked in the logs, still no ip:

I checked my SAB 0.7.9 setup with a missing API key, and the *warning* indeed does NOT contain the IP address. The IP addres is only in the "real" logging *if* you have set the level to DEBUG.


No IP in Warning: ... IP is in Debug-logging level: You can set the log level via SABnzbd: Status -> tab Latest Warnings -> Logging. Set it to DEBUG. Maybe you have to restart SABnzbd. As soon as you see the warning again, click on "Show Logging".

HTH

@Shypike: maybe put the IP address into the warning also?

Thanks sander!

Got the ip...
which is kinda weird because I run SAB on my Synology NAS. How can a 3rd party app from 127.0.0.1 try to access. Also the identifier doesn't make any sense at all..

Weird indeed.

Long shot: do you use your Synology as web proxy? Or VPN server?

Checking: you do use an OXS with Firefox 10 and a SAB plugin? If you remove the plugin from Firefox, does the warning disappear?

I'm having this exact same warning, just after I updated to 0.7.9. I've used third party programs for a year and have not had any problems, this warning just showed up out of the blue and will not go away. I've even went so far as to shutdown each program I use that plays with SAB and after everything is shut down the warning still persists.

2013-01-18 23:34:30,773::DEBUG::[interface:420] API-call from ::1 [Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17] {'output': 'json', 'limit': '5', 'mode': 'queue'}
2013-01-18 23:34:30,773::DEBUG::[interface:420] API-call from ::1 [Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17] {'output': 'json', 'limit': '10', 'mode': 'history'}
2013-01-18 23:34:30,773::WARNING::[interface:189] API Key missing, please enter the api key from Config->General into your 3rd party program: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17
2013-01-18 23:34:30,773::WARNING::[interface:189] API Key missing, please enter the api key from Config->General into your 3rd party program: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17

EDIT:

::1 is the IPv6 for localhost.... if all my programs that interact with SAB are shutdown... and nothing on my machine is accessing it... why would there be an API call?

Quick update: So by accident I opened chromes task manager instead of clicking extensions only to find a shit ton of backgrounded pages and extensions running... ended all the tasks and restarted the browser... thought to myself... I should check SAB's warnings... cleared the log and no more warnings...

I should mention that i am not running any extensions on chrome that interfaces with SAB... so something caused a background extension to maintain an API call... even after I restarted the computer.... it only shut down manually in chromes task manager.

Fixed it for me!

Cheers

Did you change the api-key at some point?
If so, stale browser pages will be using the wrong key.