SABnzbd Forums

Hi all,

Yesterday all of a sudden SAB just stopped accepting files from Sickbeard and Couch Potato.  Everything was working perfectly before then.  I ran the SAB console and foind out that somehow the port had changed in SAB.  I dont know how or why this would have happened?  Anyway I reconfigured SB and CP to point to the new port but they still couldnt send to SAB.  SB logs show the following:

SEARCHQUEUE-BACKLOG-248683 :: Unknown failure sending NZB to sab. Return text is:

I then uninstalled and reinstalled SAB - same issue.  Another strange thing is that I access SAB on localhost:8080 - this is also where SB and CP are pointing, however I tried manually downloading from NZBMatrix and when the nzb file was opened, a new page in my browser opened for SAB (even though it was already open) but on port 8085!  Why would this be?  I then tried reconfiguring SB and CP to point to 8085 but again, I get the same issue.

I have no clue what could have caused this.  The only thing I did yesterday was run both IOBit Malware and Malwarebytes.  Could running these have caused the SAB issue?  Its the only thing I can think of - but I dont know how to fix this!

Any help would be appreciated.  Thanks!

When SABnzbd starts up and finds out it cannot use it designated port,
it will start looking for an alternative port.
An already running SABnzbd means that the second instance will use another port.
The 0.6.x releases have an issue on Windows 7 with an HTTPS-only WebUI.
But any other program blocking 8080 makes SABnzbd look for another port.

There's room for improvement in SickBeard, because the 0.6.x's
advertise their contact URL in the registry.

So how can I get this working again?  It really seems like something to do with SAB configuration - but I really dont know!

Thanks for your reply.

SABnzbd remembers the last port it used in the INI file.
That's a bit inconvenient actually. Not saving it could be confusing as well.

To repair: stop SABnzbd.
Edit the sabnzbd.ini file, look in the [misc] section for host.
Otherwise start it once with the extra command line parameters
--server localhost:8080

Thanks this partially works however whenever I add an NZB, SAB opens a brand new window and new instance of SAB and changes the port, even though SAB is already running and open on the existing port.  This then changes the ini to the new port.  This happens every time I open an nzb file.  I could open 10 nzbs and there would be 10 new occurences of SAB all with different port numbers!  

Any idea how new NZBs can just go directly into the existing instance of SAB?

What you describe is a known issue with 0.6.x
Read here for a work-around until 0.6.3 is out:
http://forums.sabnzbd.org/index.php?topic=7182.0

Thanks for that - however I dont have HTTPS enabled?  I did have it enabled upon install as an error but changed it immediately.  Would a fresh install without choosing HTTPS help?

Maybe the NZB extension is coupled to an older version of SABnzbd.
Just re-install using the Windows installer file and make sure you check the
NZB association box.
You could check for HTTPS settings in the sabnzbd.ini file too.

Yes, there are HTTPS settings in the ini file - they are setup for port 9090.  Should I just remove them?

No, that's OK.
The problem only occurs when HTTPS does not have it own port,
but uses that of HTTP.
Does it work now?

I have made you member of the Release Testers group.
This enables you to download the pre-release of 0.6.3.
See "Release Testers" board.
I would be interested to know whether this solves your problem.

Thanks - I will check it out today.

You might better use the official 0.6.4 release now.