FYI: Chrome and https://127.0.0.1:9090/sabnzbd
Posted: May 27th, 2016, 9:20 am
A FYI for Chrome / Chromium users:
If you access https://127.0.0.1:9090/sabnzbd, Chrome will complain, saying
You can instruct Chrome to skip that: In Chrome, open
Chrome will say:
You can now access https://127.0.0.1:9090/sabnzbd without Chrome giving a separate warning page. You still get a strike-throught sign in your HTTPS symbol in the address bar, which is correct.
This works for localhost / 127.0.0,1, not for SABnzbd on remote devices.
If you access https://127.0.0.1:9090/sabnzbd, Chrome will complain, saying
Then you have to click Advanced, etc.Your connection is not private
Attackers might be trying to steal your information from 127.0.0.1 (for example, passwords, messages, or credit cards). NET::ERR_CERT_AUTHORITY_INVALID
You can instruct Chrome to skip that: In Chrome, open
Code: Select all
chrome://flags/#allow-insecure-localhost
Click on Enable, and restart Chrome.Allow invalid certificates for resources loaded from localhost. Mac, Windows, Linux, Chrome OS, Android
Allows requests to localhost over HTTPS even when an invalid certificate is presented. #allow-insecure-localhost
You can now access https://127.0.0.1:9090/sabnzbd without Chrome giving a separate warning page. You still get a strike-throught sign in your HTTPS symbol in the address bar, which is correct.
This works for localhost / 127.0.0,1, not for SABnzbd on remote devices.