SABnzbd Forums

I am getting this error "2013-09-04 23:29:49,178::WARNING::[interface:189] API Key incorrect, Use the api key from Config->General in your 3rd party program: ::1>Python-urllib/2.5" in sab. I have SB running and its working fine. New releases are being sent and processed. I just installed CP and I checked all settings, but have not seen it in action. I have checked the API in CP and it matches what is in SAB. Is there anything else that has the sab API key that I am missing?

It's about the API Key, not about the API, so I've changed the title.

Finding the program with the bad API key is easy:

stop all programs CP, SB, etc
in SABnzbd, click on Clear Errors
Now wait a few minutes: are all errors gone?
If so, start CP. Do the errors occur? If so, you have found the program with the bad API key. You know where to fill out the API key in CP, so ...
If needed, continue with SB.

HTH.

Thanks for the reply and suggestions. I have tried what you suggested and there are no errors that show up from either SB or CP after shutting them down and starting them individually. I found that its when I download an nzb, and open it thats when the error occurs. I can download an nzb and add it through SABnzbd console and that will work. I dont have any plugins for my browser active that interface with SABnzbd, and SABnzbd is the default application for nzbs, is there something with the file association and SABnzbd that would cause this error?

OS is win7

" your 3rd party program: ::1>Python-urllib/2.5" means the program using the API is running on your local system, and uses Python-urllib/2.5. That looks like SB or CP to me, and not a browser plugin (which uses Javascript). And the error messages are gone when you shutdown SB and CP, so that proofs it too.

Anyway, if you're sure it's not SB nor CP, there is a brute force way to stop it: change SAB's port from 8080 to 8085, (and HTTPS from 9090 to 9095). Check that the API error message is gone.
Then go into SB, and change the URL of *SAB* to contain 8085. Check that 1) the API error is still gone and 2) SB is working. Then proceed with CP.

Warning: only do the above if you know what you're doing. And If the problem is in SB or CP (as I think), you will get the error message back afterwards. That is then the 100% proof the problem is in SB or CP. If the problem is not in SB or CP, the error message will be gone.

I also have the same issue, But only on one machine. The main difference in SAB config is authentication.

When you manually download a NZB and windows tries to open it with the default program of SAB via file associations. I suspect its the http authentication to SABclient which i use that a causes the error. Windows does not support API access or does not pass through the SAB username or password. The work around is to manually upload NZB into SAB.

ksero ... any update from your side? Problem solved?