Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import intermediate CA cert to Certificate Authorities in web GUI #4

Open
danb35 opened this issue Apr 11, 2018 · 8 comments
Open

Import intermediate CA cert to Certificate Authorities in web GUI #4

danb35 opened this issue Apr 11, 2018 · 8 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@danb35
Copy link
Owner

danb35 commented Apr 11, 2018

The script imports the CA cert as part of the server cert (it uses the fullchain.cer file, which includes both), but it doesn't separately import it into the Certificate Authorities in the FreeNAS middleware. This shouldn't be necessary for web GUI purposes, but might be helpful for other uses. Would want to check if the same CA is already present before importing a new one, though.

@danb35 danb35 added the enhancement New feature or request label Apr 11, 2018
@Cloud-Kid
Copy link

Hey !
I have the same problem here, I know a bit about IT and networking but I don't want to mess with the script at this point, any fixes ?

@danb35
Copy link
Owner Author

danb35 commented Jan 9, 2020 via email

@danb35 danb35 added the wontfix This will not be worked on label Jan 9, 2020
@Cloud-Kid
Copy link

Hey !
Thanks for the fast answer, can you tell me what's an "IMO" and how I can manage this to work basically ?

Thanks again for your project :)

@danb35
Copy link
Owner Author

danb35 commented Jan 13, 2020

"IMO" = "in my opinion". I'm not quite sure what you mean by your last question--to manage the script, download it, prepare a configuration file, and in the most common use case (or at least the use case I had in mind when I wrote it), call it from your ACME client (certbot, acme.sh, or whatever else you like). That client will handle obtaining/renewing your cert from Let's Encrypt, and then it will call this script to deploy the cert to your FreeNAS server. I think this is pretty well discussed in the README--were there parts that were unclear or incomplete?

@Cloud-Kid
Copy link

Thanks for the translation !
I mean everything seems to work fine, certificates are created and stored, I can see them in my freenas structure. But when I connect to my web GUI I can't select any SSL certificate, so do I need to move them in a very special place ?

That's the only thing I can't figure out at the moment

In one question : Where the certificates/keys need to be placed in order to allow their selection through the freenas web GUI

Capture d’écran 2020-01-21 à 15 06 21

Capture d’écran 2020-01-21 à 15 06 28

@danb35
Copy link
Owner Author

danb35 commented Jan 21, 2020 via email

@Cloud-Kid
Copy link

I can see the CERT/KEY by following this path "/root/.acme.sh/mydomainname.com" and i have 0 error by executing your script, maybe i've done something wrong ? I'm gonna try again and delete every stuff under this path beforehand, that's really strange because your script looks nice and it's seem pretty straightforward.

Thanks for your understanding

@danb35
Copy link
Owner Author

danb35 commented Jan 21, 2020

Please open a new issue--once again, the problems you're seeing have nothing to do with importing the intermediate CA certificate. And when you open that new issue, post the complete output of running the deploy_freenas.py script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants