Fair enough. The vhost subdomain was created to avoid a condition where visting the FQDN:80 or :443 would return a configuration error. Since...
@remkoh How do you reconcile your position that serverhostname in the control panel FQDN is invalid when that is the configuration that's always...
I had to move forward. That surgery seems to have worked. The questions remain about whether that was correct and about the FQDN.
I think this is simpler than it seems. I'm sure I haven't communicated properly. I'm no longer running mail services. Certbot was never installed...
@till wrote > I'm quite sure you did not have the same config on previous ISPConfig installations as you now use acme.sh and have previously...
I have, for example /var/www/sub1.site.tld/ssl, with acme (LE) certs. That ssl folder contains files: sub1.site.tld-le.crt sub1.site.tld-le.key...
Related to old files, I just created https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6913 "/var/www/*/ssl symlinks not removed after...
Thanks for that confirmation. I was running 3.2.1 until this year. I think my most recent ssl file backups are from 12/2023. I'll delete those old...
I'm not aware of such a rule. Can you explain that? In /root/.acme.sh there is a folder for hostname.domain.tld which is a virtual host created...
I don't have anything custom - I'm not competent with acme or LE interfaces to do that yet. I used the migration tool, upgraded to 3.2.12. This is...
ROFL : Ooops: I see in the 3.3 release notes: > Auto Cleanup of Certificates: Old certificates will be automatically removed, reducing clutter...
I'm sorry if I've missed other notes about this, it's tough to search on this topic. In April I migrated a system from 3.1 to 3.2....
All certs on my v3.2.12p1 system update and all sites on normal :443 seem to get the new keys. In June, Acme issued the ISPConfig dashboard itself...
Separate names with a comma.
