Page 1 of 1

SABnzbd Crashing High Sierra (Mac)

Posted: November 15th, 2017, 9:29 am
by deebee
Hi,

Has anyone encountered an issue where SABnzbd crashes their WiFi on Macs running High Sierra? Since I upgraded the OS, everytime a program starts downloading through SABnzbd, the WiFi crashes and I need to reboot.

I've upgraded to the latest version 2.3.1 but it still happens.

Thanks,
Damian

Re: SABnzbd Crashing High Sierra (Mac)

Posted: November 15th, 2017, 11:13 am
by safihre
What if you limit the speed to about 80% of your maximum performance? Or just start really low.
Sounds like a wonkey driver for the network or an over-active virusscanner/firewall?

Re: SABnzbd Crashing High Sierra (Mac)

Posted: November 15th, 2017, 6:52 pm
by deebee
Thanks - Will give it a go & let you know

Damian

Re: SABnzbd Crashing High Sierra (Mac)

Posted: November 17th, 2017, 7:56 am
by deebee
Limiting the speed didn't help. Any other ideas?

Damian

Re: SABnzbd Crashing High Sierra (Mac)

Posted: November 17th, 2017, 8:43 am
by safihre
What happens when you just use 1 or 2 connections (for testing) to your newsserver? If that works fine, increase the number of connections again.
Do you use any special security software?

Re: SABnzbd Crashing High Sierra (Mac)

Posted: November 19th, 2017, 8:48 am
by deebee
Limiting the connections did the trick. Am slowly building back up (currently up to 10) to see if I can figure out the magic number that causes the problem

Re: SABnzbd Crashing High Sierra (Mac)

Posted: November 21st, 2017, 7:23 pm
by videopayphone
deebee wrote: November 15th, 2017, 9:29 am Hi,

Has anyone encountered an issue where SABnzbd crashes their WiFi on Macs running High Sierra? Since I upgraded the OS, everytime a program starts downloading through SABnzbd, the WiFi crashes and I need to reboot.

I've upgraded to the latest version 2.3.1 but it still happens.
I'm encountering the same problem. I've tried limiting my download speed and the number of connections to my newsserver and neither has solved the issue.

Turning my wifi off and back on again solves the problem temporarily.