Support Forum

It has something to do with the certificate storage on your specific computer.
For some reason it doesn't like the certificate for Astraweb or one of the authorities that signed the certificate.
This could maybe be due to some security software you use?

We have been trying to fix this issue for a while, but we haven't been able to pinpoint it. What did you change from the default settings? For example: 'Check before downloads' turn on? 'Download all par2' ? 'QuickCheck'? What could maybe help (but is pretty invasive) is starting SAB with the parame...

We opted to keep those Glitter specific things out of the INI.

Everything below the grey line in the window is not stored in the INI.
That's not very intuitive I know...

Might consider restarting SAB every 12 hours or so. You can do this using the Scheduler.
Python is not too good in memory management so things build up over time.
Do you run sabnzbd as a service?

Reduce your Article Cache to 500M or lower.
3.1GB.. Wow.
How many jobs were in the queue? How big were they?

Great!

Hmm, can you install any version? Maybe 0.6.13?

Because 0.6.14 came out in 2015, so surprised it says any 2016 dates on the wiki.
Could be they use the latest develop version which still is tagged as 0.6.14 since they never released a newer one.

Unfortunately par2cmdline is very picky about basepath, not even really sure what it considers basepath. We really never had problems with 0.6.14, it's shipped with the Linux version of Sab for this reason. Very strange. But since we want to support future versions of par2cmdline I better just add d...

Set the logging to Errors/Warnings and nothing is logged except crashes. This is the default setting when installing Sab. I think this is the default setting for new users.
You can remove all history items by clicking the little trash can icon in the right bottom of the interface.

They are not forgotten in the browsers I tested, they are saved in localstorage.
Maybe you clear this or some browser plugins clear it?

Could you provide a screenshot?
This way I can better understand the problem

Problem identified from the logs:
Using a version of par2cmdline newer than 0.6.14 which doesn't work because it won't scan files 'out of basepath'.

So what have you set for Max line speed?
When you use Glitter skin, a slider should be present to limit the speed. This slider also shows the speed its going to limit it to.
This is is all in MB/s, not MBps.

Oke, but I will need the NZB to test what's going on!

Are you able to switch versions?
What happens when you switch back to SAB 1.0.3? Can be downloaded here: https://sabnzbd.org/download-stats
This is to exclude a change in SAB we made from 1.0.3 to 1.1.0.