Download failed - out of your server's retention?

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
rxan
Newbie
Newbie
Posts: 2
Joined: April 6th, 2012, 6:56 am

Download failed - out of your server's retention?

Post by rxan »

I haven't been able to download a single file yet. I am using news2.teksavvy.com, port 119, no SSL, connections 3. I'm pretty sure these are the right settings based on multiple forum posts. Server test worked fine. I am on DSL.

Even very recent NZBs that I got from http://nzb.su don't work. These are only hours old.

Any tips? Thanks. I'm a newb at this newsgroup stuff.
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Download failed - out of your server's retention?

Post by shypike »

Set the "group" option to on in Config->Switches and try again.
rxan
Newbie
Newbie
Posts: 2
Joined: April 6th, 2012, 6:56 am

Re: Download failed - out of your server's retention?

Post by rxan »

Setting the Send Group option on didn't fix it.

I am seeing that each one I try to download has missing articles. Could this be a problem with news2.teksavvy.com?
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Download failed - out of your server's retention?

Post by shypike »

It could be the server.
What we usally say in these situations, is try to download the same NZB
with another download app.
If you get the same result, it's the server that is the problem.
(Or it's just a bad post).
Post Reply