search

ShaneKodi / sabconnect

Automatically exported from code.google.com/p/sabconnect
0 stars 0 forks source link

seems to not work when ssl is enabled unless you first open sabnzbd in the browser #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. restart chrome
2. click on sabconnect

using sabnzbd 0.5.0 on opensuse 11.2 x64
client system: server 2008R2 x64

latest version of sabconnect

seems to not work, gives error:

Could not connect to SABnzbd - Check it is running, the details in this 
plugin's settings are correct and that you are running at least SABnzbd 
version 0.5!

This error goes away if you open up sabnzbd. could this be related to the 
fact that the ssl certificate is untrusted?

Original issue reported on code.google.com by maerz.th...@gmail.com on 15 Mar 2010 at 1:47

GoogleCodeExporter commented 9 years ago 
Exact same is happening for me on an (untrusted) ssl connection, under Windows 7

Original comment by daniel.h...@gmail.com on 25 Apr 2010 at 6:01

GoogleCodeExporter commented 9 years ago 
the problem is it's very hard to add an untrusted certificate to chrome as 
trusted, you 
have to download the certificate elsewise and import it into chrome to do it.

the best solution would be to figure out a way for sabconnect to accept 
untrusted certs 
on its own.

for now i'm just using SABSTATUS in firefox, but it sucks having firefox open 
all the 
time just to interface with sabnzbd.

Original comment by maerz.th...@gmail.com on 25 Apr 2010 at 6:31

GoogleCodeExporter commented 9 years ago 
SABConnect won't be able to allow untrusted HTTPS certificates until the end 
user himself allows it. That's just how Javascript XmlHttpRequests work.
The best way is to import the invalid certificate.
Chrome uses the OS certificate tools, so if you're on Windows simply import the 
certificate using Internet Explorer. This will add the certificate to the 
Windows datastore, and Chrome will see that.
I think it's pretty much the same for OSX, and maybe even Linux.

Original comment by guillaume.boudreau on 29 Jun 2010 at 12:55

GoogleCodeExporter commented 9 years ago 
importing an untrusted certificate is not a trivial task in chrome like it is 
in firefox. that solution is not feasible for the majority of the userbase.

Original comment by maerz.th...@gmail.com on 29 Jun 2010 at 12:32