Automated Let's Encrypt didn't work on subdomains, but manually script worked. Why?

[jlpeifer]

I noticed that the subdomains for a specific domain no longer had valid SSL certs after DA's automated Let's Encrypt process ran. I ended up running a console/terminal command manually that fixed the problem, but I'm confused why I even needed to do this. Here's what I ran that worked...

/usr/local/directadmin/scripts/letsencrypt.sh server_cert `hostname -f`,mail.domain.com,smtp.domain.com,www.domain.com,domain.com

Why would this work manually, but not automatically?

 

[jlpeifer]

Well... it's not entirely fixed. This is what Safari shows when I attempt to visit one of these subdomains. The hostname for this server is never going to match the exact domain name of the SSL cert that's generated. I have many domains hosted on this server, so its hostname is the generic one created by DA when the initial install was performed.

 

[jlpeifer]

Resolved: Followed instructions for applying Let's Encrypt wildcard SSL to the domain. Problems solved. Sorry for the false alarm.

https://azdigi.com/blog/en/webserve...all-lets-encrypt-wildcard-ssl-on-directadmin/