I searched for a solution but didn't see anything that worked. I'm running Ubuntu 9.10 with Sabnzbd 5.2 and using Sickbeard to post process. Everything was working fine until Sab stopped connecting to newshosting last week. All of my accounts work with newshosting and I am able to download using other readers using the same settings. I'm having the same problem on Supernews (subscribed today thanks to the recommendations of this forum).
When I restart I get the following error:
WARNING: API Key incorrect, Use the api key from Config->General in your 3rd party program:
All of my API Keys for Sickbeard and nzbmatrix.com are all correct, even after regenerating them. Restarting Sab causes it to reconnect to all 10 connections of the newserver and then disconnects and gives me the API errors.
Any ideas of where I should start looking for a solution?
Thanks!
Version: 5.2
OS: Ubuntu 9.10
Install-type: Linux repository
Skin (if applicable): Classic - Dark Blue
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? Yes
Sab not connecting to newsgroup provider anymore
Forum rules
Help us help you:
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.
Sab not connecting to newsgroup provider anymore
Last edited by Blown 89 on May 14th, 2010, 3:21 pm, edited 1 time in total.
Re: Sab not connecting to newsgroup provider anymore
The two problems are unrelated.
If SABnzbd complains about the API key it is only because it receives API calls with the wrong key.
The nzbmatrix key does not have any relationship with SABnzbd's own API key.
I cannot explain the connection problems with the new servers,
other than suggesting to clean your queue.
Start once with the --clean option to remove all debris from the cache folder.
You'll loose the content of the queue.
If SABnzbd complains about the API key it is only because it receives API calls with the wrong key.
The nzbmatrix key does not have any relationship with SABnzbd's own API key.
I cannot explain the connection problems with the new servers,
other than suggesting to clean your queue.
Start once with the --clean option to remove all debris from the cache folder.
You'll loose the content of the queue.