Okay, so I have certbot on my main web server (its been running a while) its currently running on 3.2.5 so it seems the upgrader handled it without issue, I just tried to add a website and the ssl failed, I am not sure that issue is worth looking into at this point. How painful is it going to be to migrate the websites if I set up new host with acme.sh installed?
To me changing to acme.sh should be easy though there worries by some quarters and I already put forward my theory on how to do it for few months already.
There is no reason to do that, certbot works perfectly fine with ISPConfig 3.2.5 and it will continue to work fine in future. Most of my systems use certbot and all of them are working fine, I will not migrate any existing system to acme.sh. So unless you reinstall a server from scratch where you plan to delete all certs anyway, do not switch to acme.sh. And for the reason why certbot fails on your server, you'll probably just have to install a newer version as described on certbot website. Use Let#s encrypt error FAQ to find out why it fails: https://www.howtoforge.com/community/threads/lets-encrypt-error-faq.74179/ Or just install a new version using snap as described on https://certbot.eff.org/
Thank you Ahrasis, Till. If as you say certbot is still going to be supported then I will not bother messing with migration for now just upgrade certbot per tills suggestion. At some point in the future I may take a dive into Ahrasis theory. But for now, all can be left as it is, again, thank you Also, I am fairly certain that this server pre-dates snap being used in ubuntu or at least being prominent, certbot was not installed using it that much I am certain of. Looking into this it seems they are independent and snap does not replace a version installed with apt and vice versa. I will take a look at the certbot website for the next steps, thank you.