SABnzbd Forums

Hi!

I've recently switched to Chromium, which seems to be way more paranoid when it comes to SSL certificates.
I'm using a self-signed certificate (connecting only through https) and sometimes retrieve data from an indexer that allows me to send NZB files directly to SAB (upon setting an API key).
For ease of use, I'm also using some dynamic DNS as my IP changes from time to time.

All was fine until Chromium.
It likes to complain about that self-signed certificate when I'm using the web interface, but I can easily bypass that.
The real issue is that I cannot bypass it when I want to push that little button to send those NZB back to SAB, throwing (on console) this error: net::ERR_INSECURE_RESPONSE.
I tried importing the certificate but it doesn't want to be imported, at least not in that "Trusted Root Certificate Authorities" section.

Has someone managed to fix that?

Which route do you use for the NZB:

Indexer -> Chrome: NZB on localhost -> upload to https://127.0.0.1:9090/ ?
or
Indexer -> directly to SAB, bypassing Chrome?


And: which indexer do you use?

I don't know how exactly the indexer (nzbs.org) sends the NZB.
Until now, I set my DynDNS as the URL. I thought it was sending the NZB directly to SAB.

Reading your answer, I tried using "localhost" just in case, and it works. Thanks for the clue.
Don't know if that's better but as I'm only using the indexer on this computer, it'll do