Support Forum

On the main page, below the history on the right there is the button to toggle the Archive.
This is where jobs go if you delete them from the history, just like in your email client etc. You can also choose to permanently delete jobs directly if you don't want an archive.

Nee, dat is niet wat die optie doet.
Volgens mij heb je de Sonarr-basis-map ingesteld als dezelfde map waarin SABnzbd zijn bestanden wegschrijft.
Je kan die veel beter op een andere plek zetten.

Wat heb je precies uitgezet?
Maar als je Sorteren bedoeld, ja dat kan problemen geven.

I think you are either using the Safe start option or somewhere in the script or shortcut that you use to start SABnzbd, the --server command line parameter is used.
This overrides user configured host and port one on startup.

Yes, if you have Duplicate Detection enabled it indeed will trigger. Since they are duplicate file names

Enable Debug logging in the Status window and then after it happens again click Show Logging.
In the log, it will show a Traceback why it failed to run it.

You can't. Add them separately maybe?

If you can reach Sab from your computer, then Sab is configured correctly.. It doesn't know the difference if it's exposed to the internet or not.
Have you checked the Synology firewall settings?

Als je deze melding krijgt staat daar als het goed is nog meer informatie bij, bijv in de details van de download of anders in de logs. Hoeveel heb je aan de instellingen aangepast? Krijg je het probleem ook bij de 100Mb test download in Status and Interface settings scherm? Kan ook Windows Defender...

Yes this is by design, to avoid having multiple identically named jobs in the queue.

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?