Oh sure, it’s the SAN cert for postfix and dovecot configuration thing. I am not understanding where the cert containing this certificate containing all domains is created when running a command like:
letsencrypt certony --webroot
–webroot-path /var/www/vhosts/example.com -d example.com
–webroot-path /var/www/vhosts/domainvirtualhost1 -d domainvirtualhost1
–webroot-path /var/www/vhosts/domainvirtualhost2 -d domainvirtualhost2
The issue I have is all my domains are spread out with virtualmin so each resides in /home/domain/public_html locations where "domain is the name of the admin user created for that domain. It happens to match the domain without the .com on the end in my case.
www.domain1.com is located at /home/domain1/public_html for instance. the only common directory in the path is /home and no site for webroot to send to lets encrypt is locaqted there. Does that make sense? As i read this there has to be a common path as a parent with a site associated with it as in /var/www and /var/www/domain1
I have been at this for a lot of hours and tried numerous things. I have a dovecot file set up for each domain in conf.d and I think that’s covering dovecot but it’s becoming a spagetti mess and one SAN cert for dovecot and postfix would make me sleep better.
I parsed the command out like that so i could look at it in steps and it depends on a website in /var/www
My websites work fine and the certs are sym linked to /etc/letsencrypt/live/website for their cers