FYI: Chrome and https://127.0.0.1:9090/sabnzbd

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
User avatar
sander
Release Testers
Release Testers
Posts: 8827
Joined: January 22nd, 2008, 2:22 pm

FYI: Chrome and https://127.0.0.1:9090/sabnzbd

Post by sander »

A FYI for Chrome / Chromium users:

If you access https://127.0.0.1:9090/sabnzbd, Chrome will complain, saying
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
Then you have to click Advanced, etc.

You can instruct Chrome to skip that: In Chrome, open

Code: Select all

chrome://flags/#allow-insecure-localhost
Chrome will say:
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
Click on Enable, and restart Chrome.

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.
Top
Post Reply

Return to “General Help”