Support Forum

Of course!

Could you maybe email me your logs and also maybe your socks5 config? Then I can try it out. You can change your username/pass after this
[email protected]

What happens if you trigger a Watched Folder readout from the hamburger menu?

That's really interesting.
Can you enable Debug logging in the Status and Interface settings window, then restart SABnzbd with Socks5 enabled.
Then add a file to the Watched folder.
Click Show Logging in the Status Window after a while and check near the end of the logging.

Unfortunately, no resolution yet. It's a low level error that we don't have any control over.

You describe exactly why this is not a high priority: for older NZB's it's never going to be complete anyway, for newer NZB's we have the Propagation Delay. The reality is a bit harder than it might seem at first: Currently we just don't keep track of which articles failed. Additionally, we don't ha...

Thanks for the extensive testing. Indeed you are right, the Retry in SABnzbd is not very smart. It doesn't really retry on article-level, only on file level. Because it already finds partial files from the first try, it keeps on using those and tries to repair those. We have a feature request for a ...

Your report is a bit hard to read, but if I understand correctly: when a download failed because of missing articles and you use Retry, it doesn't succeed. However, if you add that nzb again regularly, it does succeed even though the first time it failed? Could you enable Debug logging in the Status...

You can make selections based on size also in the RSS feed criteria. Only add certain jobs with certain keywords if they are larger or smaller than a set size.

This is by design, so you can decide if you actually want to download the NZB.
This way you can prevent API-hits on sites that have strict API-hit limits.
Only when we fetch the NZB we know it's size.
You will have to add the item to the queue not in the paused state to avoid this.

Very strange.
Can you try this:
Enable Debug logging in the Status and Interface settings window (it's at INFO now).
Restart SABnzbd.
Add another NZB.
Wait 2-3 minutes.
Click show logging in the Status and Interface settings window and send the logs to me at [email protected]

https://sabnzbd.org/wiki/advanced/directory-setup
The log_dir has your logs.

It's not widespread, you're the first one reporting it.
So let's see what 4.3.0 reports.

Could you please try 4.3.0 Beta?
What provider do you use?

It's still frustrating of course that Unraid is giving these problems. Have you tried lowering the number of connections?