I've been moving some domains into ISPConfig. Previously the domains were all manually created and managed but I've hit an issue with an SSL domain.
Our domain, call it "example.com", has an existing Key, CSR, Cert and Bundle. The certificate is for "www.example.com" and has worked ok for the last 9 months or so.
I set example.com up in ISPConfig, clicked the "SSL" checkbox & Auto Subdomain = "www" ... and added the CSR, Cert and Intermediate Cert to the relevant fields, select "Save Certificate", hit save and wait for the job queue to run.
Upon browsing to the domain "https://www.example.com", Chrome throws an error about a self signed certificate - the site is delivering the self-signed cert that was used in ISPConfig install (default vhost?).
I jump onto a shell:
* nginx -t - shows all is OK with the server config
* there is no SSL server conf file set up for example.com - it seems that ISPConfig is saving the cert but not creating the required web server config file.
* in the domain's "ssl" dir I see www.example.com.csr
- no sign of the key file, though.
In order to get the SSL domain up and running, I created a web server config file containing the required path to the cert (ssl_certificate) and the key file (ssl_certificate_key).
With a pre-existing SSL setup how do I get ISPConfig to find the key file and create the required server config file. I'm concerned that it will create the vhost file and conflict with my manually created file.
Using latest ISPConfig stable & Nginx...
Thanks in advance