Error in API key..

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
Tagden
Newbie
Newbie
Posts: 6
Joined: December 25th, 2009, 9:24 am

Error in API key..

Post by Tagden »

How do I find out which 3rd party program is trying to connect?

I keep getting 2 warnings every 20 seconds or so:
2012-11-13 08:38:07,996::DEBUG::[interface:400] API-call from ::1 {'output': 'json', 'apikey': 'cd9ced824bcd0460e32feae60b59bfcd', 'limit': '5', 'mode': 'queue'}
2012-11-13 08:38:07,996::WARNING::[interface:203] API Key incorrect, Use the api key from Config->General in your 3rd party program:
2012-11-13 08:38:08,003::DEBUG::[interface:400] API-call from ::1 {'output': 'json', 'apikey': 'cd9ced824bcd0460e32feae60b59bfcd', 'limit': '10', 'mode': 'history'}

My problem is that I have checked all my different laptops, servers, mobiles etc. that has ever used the apikey, and have tried disabling them one at a time.

So is there a way to identify which IP or something where the request came from?
User avatar
jcfp
Release Testers
Release Testers
Posts: 1004
Joined: February 7th, 2008, 12:45 pm

Re: Error in API key..

Post by jcfp »

Tagden wrote:API-call from ::1
Tagden wrote:So is there a way to identify which IP or something where the request came from?
"Remote" address is ::1 (ipv6 localhost), i.e. something on your own machine. A browser plugin maybe? If you enable http request logging in sab (command line option: --weblogging 1), the http user-agent often identifies the culprit.
Post Reply