HTTPS traffic no longer responds

[MoeenD]

After a few hours of use, the https protocol no longer works (just get timed outs), however http (no ssl) still works, I can solve the issue after restarting sabnzbd. The issue happened once I upgraded to 0.6.8, I should also note I have my own SSL cert that I created, but never had a problem with it in the previous versions.

Version: 0.6.8 Final
OS: Windows Server 2008 R2 64bit
Install-type: Windows zip
Skin (if applicable): Plush
Firewall Software: Symantec Endpoint Protection (the only virus/firewall app that I know of to work on win server box's)
Are you using IPV6? No
Is the issue reproducible? Yes

Any help would be greatly appreciated
Thanks in advanced

[sander]

Do you run any SABnzbd related plugins?
Reason: last week, there was someone with about the same problem, which turned out to be caused by such a plugin. See http://forums.sabnzbd.org/viewtopic.php ... 449#p52922

If not, can you go back to your previous SABnzbd version and see if that version has (now) the same problem?

[MoeenD]

I currently do not have any third party plugins installed, I will try rolling back and see if the problem persists :-)

[MoeenD]

Seems like rolling back one did the trick, https works fine now, and uptime has been a day or more, where the newest version 6.8 will time out after a few hours.

[MoeenD]

:-( spoke too soon, still same issue.

[sander]

And have you tried the standard cert of SAB itself?

[MoeenD]

Haven't tried that, thanks for the idea, ill give that a go and let you know if it works.

[MoeenD]

So using sabnzbd cert seems like it's working fine, any ideas why? I prefer using my own cert.

[sander]

No, no idea.

[MoeenD]

Just wanted to post an update regarding this matter, so I placed my Cert back and everything seems to be running fine. I guess it was a system specific issue that I can't reproduce, also updated to the latest version that was just released (0.6.9). Thanks to the Sabnzbd team for the fast response for help on this matter.

[bleomycin]

I just wanted to say I've been experiencing this issue for the last year at least across every release of sabnzbd, debian 5 and now 6 and multiple different machines. It's so bad in the past I would proxy sabnzbd through apache to force ssl however I'd prefer to not run apache/lighthttpd and have a cron to restart sabnzbd daily although that doesn't seem to be quite enough as it still becomes unbearably slow/completely unusable. This happens with the default ssl cert and a self generated cert as well. I'm more than happy to provide any logs/additional info that could help track this problem down.

[shypike]

We're completely dependent on the quality of the SSL libraries.
So far we never had more than an occasional complaint from Windows and OSX users,
even though they very likely outnumber the Linux users.
For the actual SABnzbd code there is no difference between http and https.
The chain CherryPy -> PyOpenSSL -> OpenSSL is outside our control.
OK, this was a complicated way of saying: I don't have a clue...

[MoeenD]

shypike, thanks for the followup :-) and letting us know, if I ever find a solution ill be sure to post here.

[bleomycin]

shypike,

Thank you for clearing that up, i wonder if a newer version of pyopenssl will be more stable? Debian ships with 0.10 however they're up to 0.12, maybe i'll try compiling it and giving it a shot to see. Until then i'll just stick with my cron restarts and possibly setup monit to restart the process automatically when it becomes unresponsive.

[ixnu]

I have this exact issue (works for a few hours, then quits responding) with a self-signed cert on Windows 7 x64 on 0.6.9. This behavior is displayed using both the API and username/pw pair.

Let me know if there are logs or other things that I can include.