How can I install my certificate?

[Grind]

Hi there,

I bought a certificate signed by a trusted CA, so now I would like to use this certificate with SABnzbd. I'm on a Mac, how do I configure SABnzbd? Where is the certificate and the key stored?

Many thanks in advance.

[shypike]

You can see in Config->General, bottom section.
It show the folder where these files are as "Default Base Folder".
You may need to add a "HTTPS Chain Certifcates" file too (normally not installed).
You should be able to get one from your certificate provider.
For the latter file you will need 0.7.3.
That's about all I know of the matter, but this may be helpful:
https://forums.sabnzbd.org/viewtopic.ph ... tes#p69363

EDIT: the chain certificate support will arrive with 0.7.4, so not with the current releases.

[Grind]

Thank you for your reply. I found the setting, but where are these files located on my Mac? I can only find them in the keychain. I have received three certificates (AddTrustExternalCARoot.crt, mydomain_com.crt and PositiveSSLCA2.crt) from my provider, how can I install them in SABnzbd?

[shypike]

The HTTPS Support section on Config-General says what the file name are.
By default they are in:
/Users/userid/Library/Application Support/SABnzbd/admin
where 'userid' is your login name.
Note that "Library" is a hidden folder.
The alternative is to put the files somewhere else and enter a full pathname for the files.
/user/grid/cert/mydomain_com.crt

Please note that currently you cannot add the "AddTrust...." file.
You'll have to wait for the Beta of 0.7.4 to come out this week.

[Grind]

Thank you very much. I put mydomain_com.crt in that folder, is there any need to replace the 'server.key' file? If so, what file replaces that one?
I'm waiting for the Beta of 0.7.4 so I can add the AddTrust file

[shypike]

You'll have to look inside the files.
"HTTPS Certificate File" starts with

Code: Select all

-----BEGIN CERTIFICATE-----

"HTTPS Key File" starts with

Code: Select all

-----BEGIN RSA PRIVATE KEY-----

"HTTPS Chain Certificates" that's the "AddTrust..." file.

[kccourier]

I am finally getting rid of my ancient Windows 7 PC and moving everything to a brand new Windows 11 Home system or at least I am trying to. I had been using a cert.pem and key.pem file from Let's Encrypt provided in the interface of my ASUS router and that was working great with SABnzbd+ 3.1.1, the last version available for Windows 7, however now that I updated to version 4.3.3 it no longer works. As I don't have my own domain name but rather am using the domain provided thru the router's DDNS service I am not exactly sure what to do. SABnzbd+ just deactivates https because of an invalid certificate and key. I tried renaming the files to server.cert and server.key but that didn't work. The certificate and key are valid but SABnzbd+ doesn't see them as such.

if anyone has any suggestions I am all ears and thank you in advance.

[sander]

What if you install sab 3.1.1 on your new PC... does it work with your certificate?

[kccourier]

That would probably work however I have finally gotten rid of the nagging warning that I should update to a newer version and I really don't want to go backwards.

I'd really prefer if there is a way to get it working with the valid certificate and key provided by my router.

[sander]

> That would probably work

Good. Can you verify that by installing SAB 3.1.1 and checking the certificate works?

> however I have finally gotten rid of the nagging warning that I should update to a newer version and I really don't want to go backwards.

If 3.1.1 works, upgrading tot current SAB is a few mouseclicks.


> I'd really prefer if there is a way to get it working with the valid certificate and key provided by my router.

Yes, that's the goal.

[kccourier]

I will try going back to 3.1.1 but it might be a few days before I get to it. I didn't see your reply until just now as I'm finally going to bed at the end of the weekend.

[sander]

After that, you could read https://forums.sabnzbd.org/viewtopic.php?t=19684

[kccourier]

I downgraded to version 3.1.1 and it still didn't like my cert.pem and key.pem files. It worked running on my old Windows 7 PC but will not work with Windows 11.