#Sabnzbd unwanted extensions update#
#Sabnzbd unwanted extensions rar#
#Sabnzbd unwanted extensions verification#
#Sabnzbd unwanted extensions password#
#Sabnzbd unwanted extensions series#

Some users were experiencing downloads being stuck at 99%.

macOS: Adding jobs could fail without any error.

Windows: Unpacking of downloads with many archives could fail.

Windows: If repair renamed a job the correct renamed file was deleted.

Block server longer on 'Download limit exceeded' errors.

Remove email addresses settings from log export.

Some users were experiencing downloads or pre-check being stuck at 99%.

#Sabnzbd unwanted extensions rar#

Failure of unpacking of duplicate RAR no longer fails whole job.Failure of recursive unpacking no longer fails whole job.Warning is shown when password-file is too large.

#Sabnzbd unwanted extensions verification#

Only auto-disconnect after first run of verification.Allow up to 5 bad articles for jobs with no or little par2.RSS-feed title is shown for URLs being grabbed.Set custom URL instead of /sabnzbd/ (in Config > Specials).Duplicate filenames in NZB's no longer rejected by default.Improved par2 handling and obfuscated files detection.Option to limit Servers to specific Categories removed.

#Sabnzbd unwanted extensions update#

Linux: Update of SABYenc to version 3.1.1 is required.by removing redundant article verification.Improved download performance 10-15% on CPU limited devices.Windows: Download with many par2 sets could get listed as failed.Windows: Unpack could fail if started instantly after previous one.MacOS: Direct Unpack could hang in case of special characters in names.API: Jobs with Force priority should always have status 'Downloading'.API: Number of bytes missing and downloaded could be slightly off.API: Correct listing of downloaded and queued files in 'get_files'.

#Sabnzbd unwanted extensions password#

Password file was loaded from disk excessively.Retried jobs would show incorrect download progress.Unexpected behavior when diskspace becomes critically low.Only warn if number of actual passwords is larger than 30.Fix yet another potential stalling issue.macOS and Windows: Installers include Mozilla CA certificates.macOS: No longer linked to system certificate store.macOS: Bundled new OpenSSL version with support for TLSv1.2.API: 'warnings' method now returns array for better handling.API: 'missing' field removed from 'queue', use 'mbmissing'.All dates and times are now time zone independent.Show progress during verification of extra files.Different icon for downloads with Force priority.Refresh-icon in Glitter when refresh rate is above 2 seconds.

#Sabnzbd unwanted extensions series#

Series Duplicate Checker can allow PROPER/REAL/REPACK versions.

Scheduler can pause/unpause jobs in specific category.

URL grabbing can now be individually paused.

Job title from RSS-feed is shown for URLs being grabbed.

Slight performance improvement when fetching RSS-feeds.

Auto disconnect (if enabled) only after verification of last item.

Article-state (which servers are tried) is preserved after restart.

Using Hotio's docker 3.5.3 (bca9f3b), i can confirm this worked previosuly, but probably 3.3 or 3.4 the last time i confirmed i saw this work properly. Is there anything we can do about finding this problem or is it an expected change in behaviour? There is a trace file on gist dot github dot com/BM118/ea3bb02f7edf56d175af86ecd6588a0fĪpparently I am not allowed to post links yet I have tried it with enabled and get the exact same error so I don't believe it is that. As per the log it references possible duplicates as the reason for it, but I have duplicate detection disabled. EXE being detected and moved to the bottom as a failed download due to unwanted extensions. At that time, in the Sab GUI, I can see the download listed, but then errors about. please see the trace log from Sonarr, lines 15-18. This then causes Sonarr to keep re-trying the download. But the moment I have this enabled it breaks again. If I change unwanted extensions to 'Off', Sab will accept the same download request and go through the motions of downloading. I presume this is because it no longer knows that the release has 'failed'. Simply put, when I have Sab setup to abort when unwanted extensions are detected it correctly aborts but advises Sonarr differently then however it has before and this fundamentally breaks the way Sonarr then works internally as it doesn't reject the release. I originally posted this to the Sonarr guys, but they have identified Sab as causing the issue.