I have made a new multiserver setup based on the newest tutorial with the autoinstaller. The cert for the panel was created during installation, lets say https://panel.firstdomain.tld:8080. Now I want to have a second name https://panel.seconddomain.tld:8080 to access the panel. How can I add this name to the letsencrypt cert, so that it stays with all ISPConfig updates that are comming? Should I just run certbot manually?
Create a website panel.seconddomain.tld, get certificate for that website (tick on Let's Encrypt or SSL in website settings), wait 2 minutes, and the certificate should be there. If not, these instructions have info on how to debug errors: https://www.howtoforge.com/community/threads/please-read-before-posting.58408/
This is not working, because the ISPConfig Website already has a cert assigned (can be seen in the apache config). Creating a new website just assigns the cert to this new website. The site can be accessed with https://panel.seconddomain.tld but when I add :8080 to get to the Administration of course it takes the cert from this side and then complains about the name not matching the cert. I think this was different in the past, but now the new auto installer directly creates the cert. Any other ideas?
You can reverse proxy from your second domain on port 443 to the actual panel on port 8080. You could setup a single certificate that includes all secondary domains and change symlinks so port 8080 uses it, but you are limited to 100 names in a certificate, at which point you have to use a reverse proxy setup to configure more.
Because I only need one additional name not reverse proxy is needed. But now I got another problem. Seems that ISPConfig now is no more using certbot. On my single server installation this was the case. Certbot was installed and the certs were all inside /etc/letsencrypt. Now in this new multiserver setup certbot is not available, also no /etc/letsencrypt. But certs are done without problem. Seems that ISPConfig now uses another tool to create the certs - can you tell me how certs are done now?
acme.sh in /root/.acme.sh/ and actual certs are created in /root/.acme.sh/<domainname>/ certs are copied to expected ssl file locations, not symlinked back to the original files.
