Hi! After some heavy errors on my old server after upgrading to ispconfig 3.2, i decided to move to a new server (Debian Buster). We did the necessary work by following https://www.howtoforge.com/perfect-server-debian-10-buster-apache-bind-dovecot-ispconfig-3-1/ Then old server is known as coffe.maindomain.com Then new server is known as milk.maindomain.com On the new server is a testdomain established called testdomain.net, webspace and mailservice is running. I used the ispconfig-builtin SSL-certificate-LE to "secure" this webspace. I write this down, maybe this is important because of botcerts handling of the "maindomain.com". ispconfig 3.2 is running well, if I access the webinterface https://milk.maindomain.com:8080, the certificate is valid (green symbol in Firefox, verfied by LetsEncrypt) If I access the main-webspace by https://milk.maindomain.com - a certificate-warning appears. On the default-webspace https://milk.maindomain.com is now the certificate for testdomain.net active. Therefore the error, i think. How can I change this behavior? Thanks for hints! Martin
You probably created a Let's Encrypt certificate for the panel when installing ISPConfig. But the website "milk.maindomain.com" doesn't exist yet, so it shows the content of the first active domain, testdomain.net. So you should add milk.maindomain.com as a website and enable LE for it.
Thanks for that answer! Is it safe to do that? Because of the new ispconfig-certificate-function (SSL for postfix, FTP, dovecot) Since my old server is full of bugs because of the new function i am careful ... How get the ispc-panel its LEcert if the domain and subdomain of the FQDN is occopied of an virtual host? Sorry for this questions, but i want to be careful.
Yes, it should be no problem. What do you mean with full of bugs because of the new function? Maybe it is better to fix that instead of doing a complicated migration? What do you mean with
My question above in detail: ISPConfigs 3.2 new feature – Support for requesting a Let’s Encrypt certificate for the panel, Postfix, Dovecot, and Pure-FTPd on install/upgrade This feature I want to use. On my old server I did this by following https://www.howtoforge.com/community/threads/letsencrypt-on-mail-server.73695/ the tut for the panel is unknown. I upgraded from 3.1 to 3.2 *without* using the new feature. But after the upgrade the mailsystem had crashed. We were not able to recive any mails but we could send. This happend two times - so I want to leave the old system. I got support from ISPConfig Business Support which helped enormously fast and competent to re-run our services. But i think the old machine become a bit unstable over the years. So i thought its a good point to start a new server - without any testing-experiments which I did on the old years ago. On the old machine exists your described subdomain "coffe" and because of the mail-issue-experience i am now more careful. For my better understanding and of course some learnings, i ask how get ISPConfig-panel its LEcertificate if I use milk.maindomain.com for my personal hosting. Thanks for a short explain!
Alright. I haven't used the new system to get a certificate for my services so I am not sure if adding a site with the same domain as your hostname would conflict, though it should not. Maybe @ahrasis can tell you more about the implementation.
