Hi i am just migrating to new hardware, i installed ispconfig on the new server (Debian 12) using the autoinstaller (nice tool btw!). on my first dry run, i was suprised by the warning: the old server uses acme.sh, on the new server i ran htf-common-issues.php, the outputs letsencrypt section was empty, investigating further showed, that there was an /etc/letsencrypt directory created by the package ntpsec (ntp dependency). my solution ended up renaming /etc/letsencrypt and manually installing acme.sh as decribed in the perfect server setup: Code: curl https://get.acme.sh | sh -s i am not sure but i think ntp was installed by the autoinstaller and it may lead to the situation that no letsencrypt client gets installed?
I have not seen that issue on any auto-installer installation yet and ISPConfig itself downloads acme.sh automatically when its not there before it runs the command. ISPConfig checks if the command certbot is there, not if /etc/letsencrypt is there. Might just be that the existence of that directory triggered the warning in the Migration Tool. Which exact auto-installer command did you use?
the command i used was: Code: wget -O - https://get.ispconfig.org | sh -s -- --lang=de --use-php=7.4,8.0,8.1,8.2 --use-ftp-ports=40110-40210 --no-quota --ssh-port=23230 however /root/.acme.sh was not existent on the new server, the only entry regarding letsencrypt in the installer.log is: Code: Mo 18 Dez 2023 01:03:06 CET - [ISPConfig] - /tmp/ispconfig3_install/install/lib/installer_base.lib.php, Line 3689: EXECUTED: chmod +x /usr/local/ispconfig/serve r/scripts/create_daily_nginx_access_logs.sh /usr/local/ispconfig/server/scripts/create_jailkit_chroot.sh /usr/local/ispconfig/server/scripts/create_jailkit_prog rams.sh /usr/local/ispconfig/server/scripts/create_jailkit_user.sh /usr/local/ispconfig/server/scripts/ispconfig_update.sh /usr/local/ispconfig/server/scripts/l etsencrypt_post_hook.sh /usr/local/ispconfig/server/scripts/letsencrypt_pre_hook.sh /usr/local/ispconfig/server/scripts/letsencrypt_renew_hook.sh /usr/local/isp config/server/scripts/run-getmail.sh /usr/local/ispconfig/server/scripts/update_from_dev.sh /usr/local/ispconfig/server/scripts/update_from_dev_stable.sh /usr/l ocal/ispconfig/server/scripts/update_from_svn.sh /usr/local/ispconfig/server/scripts/update_runner.sh /usr/local/ispconfig/server/scripts/update_stable.sh and: Code: Mo 18 Dez 2023 01:03:03 CET - [ISPConfig] - /tmp/ispconfig3_install/install/lib/installer_base.lib.php, Line 2948: EXECUTED: mkdir -p /usr/local/ispconfig/interface/acme Mo 18 Dez 2023 01:03:06 CET - [ISPConfig] - /tmp/ispconfig3_install/install/lib/installer_base.lib.php, Line 3578: EXECUTED: chmod -R 755 /usr/local/ispconfig/interface/acme
Autoinstaller causes problems mainly when the host is not empty when autoinstall starts. Was you host freshly installed Debian 12 minimal install, nothing extra installed or configured?
not very much was installed before running the autoinstaller, i installed the system using debootstrap, chrooting, installing grub, mdadm, lvm2, zsh, smartmon-tools, rsyslog nothing else.
I'll have to make a test run of the auto-installer to see if there are any issues or if something changed in Debian 12 since the last test which caused this.
I ran the installer and acme.sh gets installed correctly even if /etc/lestencrypt is there, so there is no issue with the auto-installer. Code: root@server1:~# ls /etc/letsencrypt/ renewal-hooks root@server1:~# ls /root/.acme.sh/ account.conf acme.sh acme.sh.env deploy dnsapi http.header notify root@server1:~# Not sure, maybe you did not check for acme.sh in the correct directory, it is located in /root/.acme.sh/ folder. So what remains is that the Migration tool shows a warning when the /etc/letsencrypt folder is there. I'll check with the developer of the tool if we can improve that check somehow by e.g. checking if /etc/letsencrypt/accounts/ folder exists.
thanks for checking, good to know it works correctly. i am sorry for wasting your time - it's quite possible that only my system has been affected, and the issue was not a big deal. (history shows i entered ls /root/.acme* and i am sure there was nothing, this is why i installed acme.sh manually)
