Support Forum

Every missing article should directly jump to the next server, or at least with minimal delay.
Strange.

Wondering why you need to be in the Config so often?

If it's onky available on the secondary server, then it might indeed be a bit slower. Although from 100 to 5 is quite a drop.

How many connections do you use for all your servers?

The log lines are not related to the download, but to the importing the NZB's.

Missing data will always be slow, since we first try the main server which has to tell us it's missing before we go to the next server. So it can't be full speed, since 2 requests have to be made that are sequential.

Seems it did not output anything.
In any case, we don't make that script so I don't know how to debug the problem..

We fixed it.
You could use the latest Docker image I think to get these code changes.

Thanks for sharing your login!
I was able to reproduce and identify the bug in SABnzbd.
The summary is here: https://github.com/sabnzbd/sabnzbd/issues/2821

I will try to fix this in the next few days.

Could also be that they sent this as part of the previous article, that we didn't read the full output.
However, this is very strictly defined in the standard what is the end of data. So they are then doing something invalid.

I added a mouse-over info to the legacy wording.
Due to the extremely low number of systems that still run this OS'es, I don't want to spent more space on them on our pages.
Those users can Google in case of problems

That's why we have the 32bit legacy release. It uses an older Python version especially for this.
See the Downloads page.

His Complete Folder is somehow capped at 40MB/s, that's kind of strange though... Don't have a good suggestion for it.
Sometimes people at r/usenet at Reddit have some tips since some of them run the same setup.

Have you checked the Radarr logs and settings? Is Complete download Handling still enabled in Radarr?

What does the output say?
We don't make that script though...

If you are getting a mkstemp error, thats related to your OS disk. Don't know if that's the same disk?
In any case we need the whole error, then you can see what's the exact problem. Might also be permissions.

Your situation is not a regular one, for the vast majority of the users that set a network path it will actually hurt their performance.
And then they come to complain on forums/Reddit/Discord.
The message just says "should not", it doesn't block it.