Port conflicts between qBittorrent and SABnzbd now auto-recover
Posted by tomspark
I traced through a few forum posts about SABnzbd downloads suddenly stopping, and found the culprit: when SABnzbd's config file was incomplete, SparkBox 1.6.559 was accidentally assigning it the same port as qBittorrent, or worse, rewriting the Usenet provider port and breaking the connection entirely. That's fixed now — SABnzbd's web port gets set safely regardless of config state, and we never touch your provider connection. I also hardened qBittorrent's health check. Before, we just pinged the port number and called it healthy. Now we confirm qBittorrent itself is actually responding, so if two services end up fighting over the same port, the box detects it immediately and recovers on its own instead of sitting there with all lights green while your page times out. Highlights: - SABnzbd web port assignment no longer corrupts or rewrites your Usenet provider settings - qBittorrent health check now verifies the actual service, not just an open port - Port conflicts now auto-recover without manual intervention Check the Updates tab in your dashboard to pull 1.6.559 down. If you hit anything weird, post it here in d/sparkbox. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.
1 replies
Chris wrote:
One small correction to Tom's post above: the port mix-up existed in versions BEFORE 1.6.559 — this release is the fix, not the cause. If your SABnzbd downloads stopped recently, updating to 1.6.559 puts it right.