After updating to 4.3.3, I've had days of problems that I haven't encountered with any previous version.
I find downloaded material in the "fetching, checking, repairing" stages is progressing very slow, even without anything else pending in the queue for download. Through this process, I'm constantly (every few minutes) getting "lost connection to sabnzbd" while monitoring the interface through my browser.
I use Sonarr and the media is transferred to an external WD Mycloud connected via ethernet, though no other settings have changed other than the upgrade to 4.3.3.
Lost interface connection
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Lost interface connection
Hi and welcome to the forum. 
What device and OS are you running SABnzbd on?
What device and OS are you running SABnzbd on?
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Lost interface connection
I have it running on a Windows 11 Pro pc.
I may have already found the issue -
In between upgrading my sab versions, sonarr had several files pending in it's own queue to be sent to the previous sab version *(4.3.2 ?) It was these files downloading and repairing that caused the issue.
After waiting forever for some of these files, I deleted the rest that were still pending in sabnzbd and then once all processes finished, added them new, and I haven't had the problem since and everything seems to be completing at speeds I was used to previously.
There must have been some difficulty with the sonarr files transferring. To add, the external HDD I use for storage was full when sonarr pulled them, so this was yet an additional issue. I've obviously cleared up disk space since, but the combination of these things seemed to be the problem.
I may have already found the issue -
In between upgrading my sab versions, sonarr had several files pending in it's own queue to be sent to the previous sab version *(4.3.2 ?) It was these files downloading and repairing that caused the issue.
After waiting forever for some of these files, I deleted the rest that were still pending in sabnzbd and then once all processes finished, added them new, and I haven't had the problem since and everything seems to be completing at speeds I was used to previously.
There must have been some difficulty with the sonarr files transferring. To add, the external HDD I use for storage was full when sonarr pulled them, so this was yet an additional issue. I've obviously cleared up disk space since, but the combination of these things seemed to be the problem.