SABnzbd Forums

I have run into this issue with the last few releases:
1. sabnzbd is running, for example with the web interface on port 8085.
2. Download or open a new .nzb file.
3. sabnzbd opens a new instance with the interface on port 8090. The new download only shows on this interface while in progress, but appears in the interface of the first instance when complete.
4. Download or open a new .nzb file.
5. sabnzbd opens a new instance (the interface for this one could be on port 8090 again, or advance to 8095). Even if on the same port as 2nd instance, download only shows in this instance's interface until complete.

Last time, the issue was corrected when I updated to v0.7.19, but recently it's happening again. Will try moving to v0.7.20. I only found one other report of this issue, but there was no information discovered on the cause: http://forums.sabnzbd.org/viewtopic.php ... erent+port

SABnzbd tries to find an already running instance of itself,
using the Registry entry that's been created at startup.
It seems this doesn't work sometimes and then SABnzbd starts looking for a new port.
To work around this problem you could try using the poor-man's association of NZB.
See this instruction: http://wiki.sabnzbd.org/howto-associate

I tried this and it seems to be working. As always, thanks for your help!

I had the same thing happen to me. I had just installed a proxy server in my network. After having set the proxy server in all my browsers, I started experiencing this issue. It stopped as soon as I changed the proxy settings in Internet Explorer to bypass the proxy server for local addresses.