SABnzbd Forums

As topic indicates, now receiving that error in chrome (beta) as well as stable channel and can no longer view sabnzbd in a browser.
All options below were previously working.

Also tried Safari, same issue, though it allows me to supposedly update system settings to view, but when entering admin pass it just dumps back to the error page prompting me again to go thru the process I just went through, again.

OS: macOS High Sierra 10.13.4 (updated this morning, which is when this started occurring). This is the machine Sab is running on.
Sabnzbd: 2.3.3RC1 using https connections
Chrome: Version 65.0.3325.181 (Official Build) (64-bit) --- also same issue in latest beta
Safari: Version 11.1 (13605.1.33.1.2)

Tried connections from WAN IP, LAN IP, as well as hosted domain, none work.
Disabling https connections works, however I would clearly prefer to use https.

I am inclined to believe it is due to updating macOS. But not sure what I can do to fix the situation.
I tried deleting the certs, re-installing sab, to no avail.

I cannot access from chrome on Android phone. Blocked completely, same as Chrome on desktop.
I can access it from Chrome on Shield tablet.

I can still access sab in chrome on my PixelBook, running in the beta channel, though it gives the standard warning about unsecure connection, but it allows me to proceed anyway, that is what I am unable to do on the Mac however, there is no option to proceed, chrome just completely blocks it.

So not really sure how to proceed at this point. I generally only need access on the desktop, but am baffled why it still works fine for some platforms, but not others.

Any advice is appreciated.

Well this is to be expected with self-signed certificates, they were bound to be blocked at some point.
Try connecting via HTTP and then re-generating the certificates, maybe that will help?

@safihre

Thank you for the suggestion. That did indeed work.

Generated both a new cert as well as key.

While it did still give the unsecure warning, I am now able to fully proceed and view the page again.

As an aside, part of my problem was once I logged in via http it was no longer showing me advanced settings. I had vaguely recalled settings for generating certs before, but didnt see them when I got back in, thought maybe they had been removed in latest update to sab (and was too lazy to look at the wiki).

Anyhow, thank you again for the nudge!

safihre wrote: ↑March 31st, 2018, 9:39 am Well this is to be expected with self-signed certificates, they were bound to be blocked at some point.

Yes, certainly self-signed certificates. But the problem is you can neither get a real certificate on IP addresses (only on domain names / FQDNs).

So ... what can you do to get a Chrome approved connection to a (local) IP address? Google Chrome 65+ finds insecure:

1) Google Chrome 65+ finds HTTP insecure
2) Google Chrome 65+ finds HTTPS with self-signed certificate insecure
3) you cannot get a real certificate on a private IP address.

So ... with Chrome were in a deadlock with private ip addresses.

EDIT: fun fact: Apparently you can get a valid certificate on a public IP address; see https://1.1.1.1/