So we have enabled the cert for the admin portal login which to be honest is a bit hit or miss. We quite often have to run the ispconfig_update.sh --force for it to actually work on the server. This time it's not working. If you go to /root/.acme.sh/hosting.mydomain.com/ I can see it was all updated May 17 00:32 when it was due to renew If I go to /var/www/hosting.mydomain.com/ssl I can see these are the old files Jan 17 00:32 What the process for getting these the correct certs in to the correct location. I know this is mean to do automatically these days but something is a miss and happy to do a bash script when I know what I need to do. None of this has been done with manual renew using acme.sh, so not something we have broken it's just never really worked. ispconfig is currenly 3.2.9p1 Thanks
Can you share the output of these 2 commands: Code: ls -la /usr/local/ispconfig/interface/ssl/ Code: ls -la /root/.acme.sh/server1.example.com/ Replace server1.example.com with your hostname.
Hi Here we go Code: ls -la /usr/local/ispconfig/interface/ssl/ drwxr-xr-x 3 root root 4096 Nov 17 00:32 . drwx------ 21 root root 4096 May 17 15:44 .. drwxr-xr-x 2 root root 4096 Mar 25 2022 backup -rw-r--r-- 1 root root 3751 May 17 00:32 ca.cer -rw-r--r-- 1 root root 5963 May 17 00:32 fullchain.cer -rw-r--r-- 1 root root 2212 May 17 00:32 hosting.blocsmaster.com.cer -rw-r--r-- 1 root root 862 May 17 16:33 hosting.blocsmaster.com.conf -rw-r--r-- 1 root root 1716 May 17 00:32 hosting.blocsmaster.com.csr -rw-r--r-- 1 root root 196 May 17 00:32 hosting.blocsmaster.com.csr.conf -rw-r--r-- 1 root root 3243 May 17 00:32 hosting.blocsmaster.com.key -rw------- 1 root root 3243 May 17 00:32 hosting.blocsmaster.com.key.next Code: ls -la /root/.acme.sh/hosting.mydomain.com drwxr-xr-x 3 root root 4096 Nov 17 00:32 . drwx------ 21 root root 4096 May 17 15:44 .. drwxr-xr-x 2 root root 4096 Mar 25 2022 backup -rw-r--r-- 1 root root 3751 May 17 00:32 ca.cer -rw-r--r-- 1 root root 5963 May 17 00:32 fullchain.cer -rw-r--r-- 1 root root 2212 May 17 00:32 hosting.mydomain.cer -rw-r--r-- 1 root root 862 May 17 16:33 hosting.mydomain.conf -rw-r--r-- 1 root root 1716 May 17 00:32 hosting.mydomain.csr -rw-r--r-- 1 root root 196 May 17 00:32 hosting.mydomain.com.csr.conf -rw-r--r-- 1 root root 3243 May 17 00:32 hosting.mydomainr.com.key -rw------- 1 root root 3243 May 17 00:32 hosting.mydomain.com.key.next
This is because you created a web site using your server FQDN. When you renew the certs for the server via ISPConfig force update, it installed the new certs to ISPConfig ssl, not your web site.
acme.sh is only able to copy over certs to one location. You can either copy over the cert manually or try using symlinks.
