A client of mine has a IIS-website running plain http on his premises.
To convert it to https I have created a file in /etc/nginx/conf.d/aa450_client_with_iis.conf which proxies his webserver.
I'm doing this more, but not with a LetsEncrypt certificate.
With Plesk I created a website for that same domain and let it create a LetsEncrypt-certificate.
I checked the /var/www/vhosts/system/domain/conf/nginx.conf file and copied the 3 lines there and inserted these in my own configuration file /etc/nginx/conf.d/aa450_client_with_iis.conf
Because aa450_ comes takes precedence over zz010_ (of the zz010_psa_nginx.conf) it will not use the Apache server on Plesk, but that on-premises IIS-website.
All good for now (at least for 3 months)
Now I can imagine a few things go wrong...
The LetsEncrypt-bot is creatively using the website to create a new certificate (is that so?)
The files containing the certificates will have changed names upon renewal.
Or I have a new nice trick to let Plesk manage a LetsEncrypt certificate for an IIS on-premises site.
I have not used LetsEncrypt long enough to know what it does.
What do you think?
@IgorG or @UFHH01 ??
To convert it to https I have created a file in /etc/nginx/conf.d/aa450_client_with_iis.conf which proxies his webserver.
I'm doing this more, but not with a LetsEncrypt certificate.
With Plesk I created a website for that same domain and let it create a LetsEncrypt-certificate.
I checked the /var/www/vhosts/system/domain/conf/nginx.conf file and copied the 3 lines there and inserted these in my own configuration file /etc/nginx/conf.d/aa450_client_with_iis.conf
Code:
ssl_certificate /opt/psa/var/certificates/cert-X5Otet;
ssl_certificate_key /opt/psa/var/certificates/cert-X5Otet;
ssl_client_certificate /opt/psa/var/certificates/cert-n7WYbo;
Because aa450_ comes takes precedence over zz010_ (of the zz010_psa_nginx.conf) it will not use the Apache server on Plesk, but that on-premises IIS-website.
All good for now (at least for 3 months)
Now I can imagine a few things go wrong...
The LetsEncrypt-bot is creatively using the website to create a new certificate (is that so?)
The files containing the certificates will have changed names upon renewal.
Or I have a new nice trick to let Plesk manage a LetsEncrypt certificate for an IIS on-premises site.
I have not used LetsEncrypt long enough to know what it does.
What do you think?
@IgorG or @UFHH01 ??
Last edited: