So after looking through my docker logs, I was able to find this error - validate protocol negotiate failed: -11 If I google "validate protocol negotiate failed: -11" it gives hits with SMB / CIFS. So filesystem (mount) problem. Indeed you should solve that; not a SABnzbd problem. Good th...
OK. This is how SABnzbd does it: https://github.com/sabnzbd/sabnzbd/blob/develop/sabnzbd/filesystem.py#L1059 Can you do this within your docker, within the SABnzbd directory sander@brixit:~$ cd git/sabnzbd/ # go to directory with SABnzbd.py What does OS say, for working directory: $ df -h . Filesyst...
I do a lot of Usenet downloading across several SABnzbd clients. Why not one SAB client? One SAB client on a recent i3 core can handle 2500 Mbps downloads. I use sonarr to download documentaries, and it automatically pushes the downloads between 4 sabnzbd clients - the load is usually spread equall...
Did you check inside sabnzbd.log? Because when I add a broken .NZB to SAB, SAB does tell it in the GUI and in sabnzbd.log, for example 2024-04-02 17:44:50,607::WARNING::[nzbstuff:787] Invalid NZB file broken.nzb, skipping (error: not well-formed (invalid token): line 9, column 0) full logging in sab...