Hello everyone, I just moved from an older VPS with ISPConfig 3.1 (where I applied a bit altered version of these configurations) to a new one where I installed the 3.2.7p1 version. On the older host, let's call it "oldhost.domain.tld", I registered the website "domain.tld" (with auto-www) and then altered the renewal conf to include the subdomains "oldhost" and "autodiscover", so that the resulting certificate was issued for "domain.tld" with "oldhost.domain.tld" etc as alternate names, then I could link it to ISPConfig and just tell an email client to use "domain.tld" as IMAPS/POP3S/SMTPS server, and everything would be fine. On the newer ISPConfig version, a certificate is issued for "newhost.domain.tld" on install for service purposes, and registering "domain.tld" as a website results in having a separate cert that would never be used for Postfix, Dovecot, etc. My concern is how to proceed to (try to) future-proof a little bit - i.e. when I'll run an ispconfig_update.sh I'd prefer to not need to apply again manual workarounds because ISPConfig itself overwrites everything with the older config: would following "the old way" (alter renewal conf to include "newhost", etc as alternate names of "domain.tld", then "ln -s /var/www/clients/clientX/webX/ssl/domain.tld-le.crt /usr/local/ispconfig/interface/ssl/ispserver.crt", "ln -s /var/www/clients/clientX/webX/ssl/domain.tld-le.key /usr/local/ispconfig/interface/ssl/ispserver.key", rm -rf /root/.acme.sh/newhost.domain.tld) be the answer, or is there a better way to do it?
Just add the extra domain you need as alias domain to the main site in ISPConfig, or create separate sites for it if you want separate certs.
