Support Forum

I did apply this commit: https://github.com/sabnzbd/sabnzbd/commit/7b5fcbe0af4032de68207034aa21c620fffe08e4 On my QNAP with a par2cmd without wildcard support this atleast made the failed releases complete again after a retry. I guess the wildcard was to fix the repair of badly named par2 files, not...

I had the same issue and applied the follow commit: https://github.com/sabnzbd/sabnzbd/commit/7b5fcbe0af4032de68207034aa21c620fffe08e4 On my QNAP with a par2cmd without wildcard support this atleast made the failed releases complete again after a retry. I guess the wildcard was to fix the repair of ...

I did apply this patch: https://github.com/sabnzbd/sabnzbd/commit/7b5fcbe0af4032de68207034aa21c620fffe08e4 On my QNAP with a par2cmd without wildcard support this atleast made the failed releases complete again after a retry. I guess the wildcard was to fix the repair of badly named par2 files, not ...

Which version of SABnzbd is this about? Sorry forgot to mention but its 0.6.14-1. Using the debian packages: ii sabnzbdplus 0.6.14-1 web-based binary newsgrabber with nzb support ii sabnzbdplus-theme-classic 0.6.14-1 classic interface templates for the SABnzbd+ binary newsgrabber ii sabnzbdplus-the...

I recently put my sabnzbd behind an apache with ProxyPass. Now my sabnzbd instance is reachable on port 80 on the url http://bla/sab Using the smpl white theme, and today i noticed that the 'Repair' option in 'Status' points to the wrong url. Most form actions are pointing to config/blabla but the r...