Every browser will tell you that for a self-signed cert (as they should). The difference is what options they give you afterwards (i.e. to trust it anyway, add a permanent exception, etc.). Other ways out of those warnings involve manipulating the os and/or browser cert store (comes with its own dangers) or to get a more official certs (e.g. letsencrypt).
Enabling https gives error
Forum rules
Help us help you:
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.
Re: Enabling https gives error
Re: Enabling https gives error
That's why I asked you ... Chrome does not trust self-signed certificates.
One step further is Let's Encrypt ... real certificates. You will need a hostname, for example via duckdns.
One step further is Let's Encrypt ... real certificates. You will need a hostname, for example via duckdns.
Re: Enabling https gives error
Thanks! Now I understand. :-)
I am going to look at Let's Encrypt. Last question: should I only open port 80 during the creation of the certificate, or should it be open 'for ever'?
I am going to look at Let's Encrypt. Last question: should I only open port 80 during the creation of the certificate, or should it be open 'for ever'?
Re: Enabling https gives error
Only during certificate request and renewal. Plus port 443, I guess
Re: Enabling https gives error
To be complete: opening port 80 was sufficient. It works now!
I created a certificate by using DSM on Synology, I exported this certificate and used it for SABnzbd. This is valid. :-)
I created a certificate by using DSM on Synology, I exported this certificate and used it for SABnzbd. This is valid. :-)
Re: Enabling https gives error
"exported"? Do you mean you copied? If so, remember you must export it again after renewing your certificate.
To avoid copying, you could also point sabnzbd.ini's cert settings to the location where the Letsencrypt ACME tool puts them.
I use Letsencrypt for SABnzbd this way: Letsencrypt on Apache, with Apache a proxy to SABnzbd.
Re: Enabling https gives error
I know this is old, but for me the answer was as simple as copying the pem files from the LetsEncrypt's live domains directory into a place unique to sabnzbd. I had created links in cygwin but apparently SABnzbd is looking for hard files and rejects links. Probably some if (file exists) logic that doesn't account for symbolic links in Windows..?
LetsEncrypt uses a live and archive folder mechanism to link the live certificates to a rotating certificate archive. This doesn't make it easily possible to directly reference the LetsEncrypt certificates without the use of symbolic links.
For the time being, I've created a simple script that The -l copies links to files.
Hope this helps.. maybe someone with the time can submit an issue and fix this so we can simply reference the live symbolic links in LetsEncrypt.
LetsEncrypt uses a live and archive folder mechanism to link the live certificates to a rotating certificate archive. This doesn't make it easily possible to directly reference the LetsEncrypt certificates without the use of symbolic links.
For the time being, I've created a simple script that The -l copies links to files.
Hope this helps.. maybe someone with the time can submit an issue and fix this so we can simply reference the live symbolic links in LetsEncrypt.