SABnzbd Forums

Version: v1.0
OS: Windows 7 Pro x64
Install-type: Windows Installer
Skin (if applicable): Default
Firewall Software: Windows Firewall & Tomato Router Firmware v1.28
Are you using IPV6? no
Is the issue reproducible? yes

I was logged in to sabnzbd through localhsot:8080, and enabled SSL with my PositiveSSL purchased cert, using this guide. I saved the settings, restarted sabnzbd, and now not only can I not open it using https/port 9090, but I can't even access it on http/port 8080 either. I tried force-closing/stopping it, and then opening it from the desktop as an administrator, but it just idles in the taskbar for 5-6 seconds, and then vanishes.

log: http://pastebin.com/GFap2YBX

Any ideas?

Something is wrong with your certificate, judging from this line:
Error: [('PEM routines', 'PEM_read_bio', 'no start line'), ('SSL routines', 'SSL_CTX_use_certificate_file', 'PEM lib')]

You can turn off HTTPS again by pressing WindowsKey+R, then running:
%userprofile%\AppData\Local\sabnzbd\sabnzbd.ini

Find and set:
enable_https = 0

Now you SABnzbd should start again.

Cool, I'll give that a shot, thank you.

Do you know if sabnzbd only accepts a certain format/flavor of certificates? Other applications have had me do all kinds of conversion jujitsu to generate a format it's happy with.

Not sure. It's all done by the third-party web framework that we use.
http://www.cherrypy.org/
The documentation on the subject is minimal:
http://docs.cherrypy.org/en/latest/depl ... ertificate

LollyGagger wrote: I was logged in to sabnzbd through localhsot:8080, and enabled SSL with my PositiveSSL purchased cert

An official (as in: non-self-signed) SSL-cert on "localhost"? Really? Is that possible to request such a certificate? And does Chrome accept that as a valid HTTPS connection?

sander wrote: An official (as in: non-self-signed) SSL-cert on "localhost"? Really? Is that possible to request such a certificate? And does Chrome accept that as a valid HTTPS connection?

Don't see why not. Why wouldn't it? I would think Chrome would validate it the same way it does any cert.

I used it on my self-hosted NGINX web-server at home, it worked fine there.

EDIT: Sorry, I was wrong (and misunderstood what you meant). No, it doesn't work on localhost, nor should it, you're right.