SABnzbd Forums

I have been using SABNZBD for a few versions now on my Server 2k8 box and it has been working flawlessly. I been having continuous issues recently connecting to the HTTPS version of the remote access on port 9090. Let's not go into the part about opening ports, because when I remote directly into the box and open the browser with https://localhost:9090/ I still have the problem.  The problem is that the site at some point becomes unaccessible. If I restart the server or kill the SAB process I can access the remote access through https://localhost:9090 for a few hours. At some point I lose access to this site and I don't know why. I can however still access the non SSL version on port 8085 when this is happening. Also, I get no errors my browser on my server just ticks away over and over but never gets there.

Things I have tried to fix it:
1. Uninstalled/Reinstalled 0.5.6 and removed everything except the settings file.
2. Uninstalled 0.5.6 and removed everything except the settings file and Reinstalled 0.5.5 to see if that fixed my problem.


Can someone shed some light on this issue? I wasn't having this problem until about a week ago.  Before that I NEVER had any issues with this client.

Given that you removed all and reinstalled, it looks like something in your system.
Although I don't have a clue to what it may be.
Do you see any suspect messages in either SABnzbd's own logfile or the Windows logging?

Do you run it as a service?
Did you check the sabnzbd.ini for suspect settings?

shypike wrote: Do you see any suspect messages in either SABnzbd's own logfile or the Windows logging?

I have logging on, but I have not had time to graze through the messages in that log.

Do you run it as a service?

Honestly, didn't realize that was available.

Did you check the sabnzbd.ini for suspect settings?

Will do that when I check the logging. I have started to just back up my .ini file and blow away the install and start fresh. I just dread doing that considering the re-configuring involved. This whole thing is just extremely annoying since this has been working properly for quite some time now.

Running as a service is possible but not really recommended with 0.5.x.
It requires mucking about with anysrv.
However, 0.6.0 will have full service support.
I can add you to the Alpha test group.

Yea, that would be great. Is that something I can get into today?

A day later I am having the same issues. Basically, when I restart the SABNZBD server it works for a few hours and then the 9090 goes unavailable. The http-8085 works great, but https-9090 is inaccessible.

I was about to start testing with Python 2.6 and some updated modules.
Can I contact you again for some testing of alternative binaries?

yup!  I rolled my server to Windows Server 2008 R2 from just the regular 2008. Everything seems good with the 9090 port now, but I am just waiting on it to break :-). I will keep you updated, but I would be willing to test anything. I am a software developer myself so anything I can do to help!

I'm testing several alternatives.
Release 0.5.6's Python-2.5 is a few sub versions behind and PyOpenSSL is one version behind.
So I will pursue that too.

Of course Windows itself can be a factor to.
In the past we had SSL working fine on XP, while it crashed on Vista & 7.
Only very old or very recent versions of SSL worked, but nothing in between.

We didn't receive this specific complaint from "regular" Windows users.

Well so far so good. I have went 48 hours without any problems since I upgraded to 2008 R2.

And i could imagine still no problems? Im running on Windows 7 32 bit and im having the same issues. Seems like it could have something to do with the windows 7/server 2008r2 core.. maybe?

I think we can consider this case closed. With the most recent updates (beta versions) this problem has been resolved. I haven't seen it be inaccessible in some time now. I haven't posted back because I wanted to make sure. This most recent post reminded me to post :-)


Thanks for the hard work guys!

Hmm i still have the same issue on my windows 7 machine, and it has been there when i was running both 0.5.6 and now 0.6.0b4.. So for my case, i still see the same error... But i have my own thread, so hope someone can help me there