Activating LetsEncrypt for domain does not set VIRTUALSERVER_SSL_CHAIN env var

Submitted by Lucian on Mon, 03/13/2017 - 07:26

Hello,

I am using a pre/post shell script to perform nginx proxy for sites, automatically, including setting up SSL.

When setting up LetsEncrypt for a domain however no VIRTUALSERVER_SSL_CHAIN is sent which causes me to misconfigure my SSL nginx vhost.

I can work around it and check for the presence of VIRTUALSERVER_LETSENCRYPT_DNAME, but this feels inconsistent.

Can this be fixed?

Thanks, Lucian

Status: 
Closed (fixed)

Comments

Submitted by Lucian on Mon, 03/13/2017 - 07:39

Also, do you know if setting up and renewing Letsencrypt send a DOMAIN_MODIFY event?

Submitted by JamieCameron on Mon, 03/13/2017 - 18:41

Yes, this is a bug - the SSL_CHAIN field will be set in the next Virtualmin release.

Submitted by JamieCameron on Mon, 03/13/2017 - 18:41

Status: Active » Fixed

Submitted by IssueBot on Mon, 03/27/2017 - 18:42

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.