Support Forum

Indeed you already diagnosed that the last limit is your disk speed. I have seen that speeds are more constant if you throttle things a tiny bit. For example, set the speed limit to 270. It will keep the speed graph more constant and leaves just a few more gaps for Direct Unpack to work. When speed ...

Start with the suggestion in the link, then you can always increase it. Although, if you check online, with aes128 it would still take many years to decrypt, so that should be plenty in my opinion.

You experience about a 15% slowdown, which is not too bad I would say. There's just a bit more work to do with the extra ssl layer involved, having to do with how data packages are decoded in the ssl layer of openssl. You could try playing with the number of connections, or the ssl cipher: https://s...

Currently it works the same as for the Queue, with all.the operations at the bottom. But indeed, that's a bit less convenient.

What do you have the Duplicate detection set to? Discard?
Are you sure you aren't adding the jobs as Forced priority?

If you set logging to at least Info in the Status window, then in the log it will show directly below the error the actual reason why it failed.
We need that to diagnose the underlying cause.

What are the filenames of these duplicate episodes?
Can you give an example?

It's called Duplicate Detection... See Config > Switches and the wiki page that's linked from there.

Not yet.

Yes it's actually hard, because of the other valid reasons why an article is still retrying.
Trying it a few times with the 100MB test download might work.

So where is Sab, on the NAS or on your pc? Why don't you just install sabnzbd on your NAS? Check our SynoCommunity package. You can then connect your other applications to it. Although you might run into issues with Sonarr etc. If you keep Sab on your pc, how do you approach it? Did you map a networ...

Could are probably right. Our article tracking is deliberately not 100% accurate, because it's much faster this way. We have a mechanism that should check every 90 seconds for such hanging jobs and forcefully resume them. Could you pause all jobs in the queue, enable Debug logging in the Status wind...

No, but why would you want this?
It could always be done using pre-queue scripts, but I am trying to understand why this would be beneficial?

Combined.

I don't see anything special in these logs.
Could you run SABnzbd-console.exe from the SABnzbd folder.
Does it close right away?
If not, could you copy and paste the contents of the window to me (by mail probably easiest).