The above quote is taken from another recent thread and is true in the sense that acme.sh operates by installing LE certs (upon creation or renewal) to where we want them to be which in the case of new ISPConfig 3.2 implementation is directly to the SSL folder of ISPConfig or website(s). I would suggest ISPConfig to change this to /etc/acme.sh/domain/ instead and then symlink to its respective needed SSL folder, ISPConfig and/or website(s). This way the same LE certs may be used by both ISPConfig and its server website hostname FQDN. I haven't look in full the implementation of acme.sh except a few like the above mentioned case where currently creating website for hostname FQDN after having the same for the server itself may break some thing(s) since its installation folder will be changed from ISPConfig SSL folder to website SSL folder. Just a mere thought and suggestion.