Closed derrickmehaffy closed 6 years ago
Ok. We will look more deeply into le docs and see if it's possible automate integration with nodes. Alternatively for now you can upload manually your generateds certificates and private keys on ngxin admin ui (i agree that it's not the best way but for now it`s the best that tool can do).
About change where things are stored like ssl, upstreams,virtual hosts, etc:
Nginx admin and agent doesn`t know about your previous file (nginx yes but nginx-admin no). In fact what do you need its an feature to import settings from current installation, this way both sides will know about things (nginx and nginx-admin).
There is no plan to mixing folders.
Im I missing something? From the web UI, I cant select certificate files of any format. I have pulled my hair off literally, even tried changing mine to .cer and .key to try see if this works, nothing.
@arebacollins on the right side of upload browser box try select "all files". For default browser look for extensions in uppercase .CER .PEM (I`m scheduling to remove this and simplify things)
Thanks
Add an option to define location on system where SSL Certificates are stored such as:
/etc/nginx/ssl/
The reason for this suggestion is in many cases users may be using Let's Encrypt or some other SSL Cert automation (In my case I have a completely separate server that handles all LE requests and rsyncs the files to each Nginx host)
The same can also be said for existing Nginx virtual host files (Again in my case, nginx config files stored in
/etc/nginx/sites-available/
and/etc/nginx/sites-enabled/
are rsync'ed between the hosts.)Just as an example using the LE Automation Script: https://github.com/Neilpang/acme.sh
In my example: SSL certs are stored in
/etc/nginx/acme/example.com/fullchain.cer
Keys are stored in/etc/nginx/acme/example.com/example.com.key
Alternatively it would be a great idea to possibly include additional Let's Encrypt support into Nginx-Admin