Author Topic: Phantom Downloads  (Read 2346 times)

Offline flynndean

  • Contributor
  • ***
  • Posts: 4
Phantom Downloads
« on: April 29, 2012, 05:01:53 pm »
I'm having a very strange issue. I think it is dependant on the indexing site I use but I can't be sure. Most of the time I have no problem, but then occasionally I will have an .nzb file acknowledged by alt.binz and then the data seemingly begin to download as normal, but the progress will be much quicker than what I would expect with my internet connection, and then the expected data will not be in my default destination folder and there is no sign of the download.

As I said, this doesn't happen all of the time and I think it depends on the source of the .nzb file. Some thoughts on what this might be would be appreciated.

Offline Rdl

  • Administrator
  • *****
  • Posts: 4073
Re: Phantom Downloads
« Reply #1 on: April 29, 2012, 05:19:45 pm »
Check your log for explanation. Most likely it will be full of '430' errors - article not found. Outside of your server retention?

Offline flynndean

  • Contributor
  • ***
  • Posts: 4
Re: Phantom Downloads
« Reply #2 on: April 29, 2012, 05:33:20 pm »
There are 430 errors but this shouldn't be a problem with retention (I have a Super Unlimited Newsdemon Account with 1353+ retention, and the items are very recent).

Is there any other reason why a 430 error might be returned or do you recommend taking this up with my Newsdemon?

Offline flynndean

  • Contributor
  • ***
  • Posts: 4
Re: Phantom Downloads
« Reply #3 on: April 29, 2012, 05:40:23 pm »
I think I have found a solution for myself (although I still do not understand the initial problem)

By changing the Ports used within the settings using the alternative Port options given by my provider, I was able to download normally.

Offline Hecks

  • Contributor
  • ***
  • Posts: 2011
  • naughty cop
Re: Phantom Downloads
« Reply #4 on: April 29, 2012, 06:03:29 pm »
Assuming this isn't a temporary problem with one of your provider's servers:

Sometimes for old files, providers may store articles in a slow backend and take some time to retrieve them; so in those cases an initial request may result in 430, but a later request will be OK. In any case, if this happens again, you could try raising retry count/time in Setup > Connection.

For newer files, it could be an issue with articles not propagating yet to your provider, or not fully across their whole server cluster. I'd guess in that case the provider forum/other users would have more info.
« Last Edit: April 29, 2012, 06:07:34 pm by Hecks »