Hi, i have just moved another small website to the server with ispconfig, chose SSL and Letsencrypt but now the wrong certificate is linked to the website. I had that once before, any idea what the cause is? Regards, Jan
Are you sure that the wrong cert is used? What#s more likely is that the wrong site is shown (which then causes a wrong cert to show up in browser), see read before posting thread. This happens when you did not get an SSL cert for the new site, see let#s encrypt error FAQ to find out why LE refused to issue a cert to you: https://forum.howtoforge.com/threads/lets-encrypt-error-faq.74179/
Thank you Till, i have one subdomain that in DNS still points to the old server, that will be moved too. I first transferred the very small html-website and plan to move the subdomain-site afterwards so it will be located in it's own dubdirectory of the web-directory. What ist the usual way to transfer domains with subdomains? I did that before on another server with ispconfig but this one is pretty new Ubuntu 22.04 and the latest ISPConfig. I will test with a domain without subdomains first, i still have to move a lot to the new server. Regards, Jan
You can get an LE cert only for domains or subdomains that point to your server, so unless DNS has been changed, you won't get a LE cert. What you can do though is that you copy the SSL cert and key that you use on the old server (even if its a LE cert) into the ssl key and cert fields on the ssl tab and select save as action. This will temporarily add the old cert as ssl cert for the site and later after you changed the DNS, you can then enable Let#s encrypt. You copy the content and database of the site and then you change DNS. Its's the same procedure for websites with and without subdomains. Nothing has been changed, neither in Ubuntu nor ISPConfig in this regard.
You are right, this was my fault! I did not put PHP-FPM and the PHP-Version right. I just changed that and all is OK. One should not postpone moving websites to past 24.00 at night because there was too much other work to do. Thanks anyway for your comments, it made me have a look in linux on how letsencrypt works in ubuntu 22.04 which is a bit different from 20.04. Kind regards, Jan
I guess you are right, it is just that i am a bit behind, i haven't had a look at that for ages because it just works ;-) Thanks anyway. Jan
Just make sure you know which one you choose previously because the older version might have been using certbot (which need to be remove and reinstall using snapd if it wasn't before), but the new one always use acme.sh especially when setup using default setting of ISPConfig auto installer. I have learnt that migration from certbot to acme.sh fully is also possible nowadays, with a little bit of difficulties / technicalities. I hope I can write that down as a tutorial later, if nobody has done that yet.
