SABnzbd Forums

I'm new to this, but think i've got everything set up ok. I've got items queued, but they're not downloading.. when i check the connections, i get the following message:
# Connections: Failed to connect: (10060, "(10061, 'Connection refused')") 5@newzbin.com:119
how can i fix this???

newzbin.com is an indexer, you cannot use it as a Usernet server.
You need a Usenet server like Giganews.com or Supernews (see our sponsored ad).

i have newzbin and sabnzbd, but then i need a server to connect them? bv news.ziggo.nl??

aoifejan wrote:i have newzbin and sabnzbd, but then i need a server to connect them? bv news.ziggo.nl??

Are you a Ziggo customer?

You can only use an ISP's newsserver if you're a customer of that ISP. If your ISP doesn't offer a binary newsserver, you have to get a paid subscription for a news service provider.

I now have giganews, but still can't download...

when i check the connections i get the following:


Server: giganews.com

Status: Enabled

# Connections: 0

Lookup the exact settings on Giganews' help pages.
It's probably this:
Server news-europe.giganews.com
Port 119
Then you also need to add your giganews username and password.
Finally make sure the number of connections is set to something like 8.

I assume that you added NZB files to the queue?

i've checked the settings, and tested the server. now i get this message:

» Download failed - Out of your server's retention?

When you click on the failed item in History, does it say how many articles were missing?
How old is the NZB content?

In History it says that it is completed? on newzbin it says that it was posted 60 days ago.

How about the amount of articles missing?
Set SABnzbd on pauze.
Enter the same NZB again, then click on the title in the queue.
You should see a list of files.

I can only see the list of files if I restart downloading?

There are 12 files, i decided to try something smaller in case the problem was that the other item was too big.

Missing articles have now gone from 109 to 142 to 169

My conclusion: the post is simply not on the server.
Either too old or the Usenet provider acted upon a DMCA complaint.