Chrome Giving SSL Error

[jollande]

Hi,

After completing a fresh install of SAB, when i click the desktop icon, Chrome tries to connect to https://localhost:9090/sabnzbd.

I get this error message.

"You attempted to reach localhost, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Google Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site."

When I close that tab and try again, Chrome connects to http://localhost:8080/

Everything then runs perfectly. Never used to work like this, I am not sure why it has started to happen since the fresh install. What's the problem, and how do i fix it?

Running SABnzbd Version: 0.5.6, Win 7 Ultimate, E6750 @2.66, 4GB

I checked these solutions but still not sure... http://forums.sabnzbd.org/index.php?action=search2

Thanks.

[shypike]

Stop SABnzbd.
Remove these files:
c:\Users\user\AppData\Local\sabnzbd\admin\server.cert
c:\Users\user\AppData\Local\sabnzbd\admin\server.key
Start SABnzbd.

For some reason Chrome started disliking the self-signed SSL certificate.
This will make SABnzbd generate a new one.

[jollande]

Well, it definitely generated the new files but i still get the same error as it want to connect to https://localhost:9090/sabnzbd again.

[shypike]

It's probably security paranoia on the Chrome side.
Early 3.5 versions of Firefox used to be about as paranoid,
recent ones let you set up a security exception.
Please complain to Google.

[jollande]

Ok thanks mate.

[ecoSix]

Hi Roomies or @ shypike

I had the same errors after a new install on Chrome and I did as you suggested. Now I'm able to log in, but my connections looks like this.



is this safe?

[shypike]

This is normal because SABnzbd uses a so-called self-signed certificate.
Only commercial certificates from registrars will be accepted by browsers.
Obviously we cannot provide those.
In a browser like Firefox you can accept such a self-signed certificate permanently.
Most other browsers do not.

In your situation you're still protected against snooping, but the authentication part
of HTTPS is absent.
With a banking site you should never accept that risk, for SABnzbd it should be OK.

BTW: there is absolutely no reason to use HTTPS when you're using "localhost".
The web traffic never leaves your computer!

[ecoSix]

@ shypike,

Thanks and will DO!!

Great job !!

[AutomaticCoding]

Another fix (It's not really a fix, it's how it should be executed, you're the one breaking it), which is relatively easy, is, just to simply give it a legitimate SSL cert signed by a trusted CA. You can either set yourself as a trusted CA in your computer, and, sign your own cert (A bit annoying), or, use a free (less trusted) SSL company like StartSSL.