https://docs.directadmin.com/changelog/version-1.50.0.html#let-s-encrypt-automated-free-ssl-certificate-installs-skins-lang
There is an internal variable, set by default to:
letsencrypt_renewal_days=85
Check if it really same in your case, or you have old setting about 60 days.
Yes, if you have issues with, for example, 5000 accounts on 1 IP, so try to host 4500 on one IP, next 4500 accounts put on next IP and so on.
We have own IP-pools so it easier to us host no more than 500 domains/ip.
1. You can use Zero SSL for part of websites, or other ACME provider.
2. You must reconfigure to ask new cert not after 60 days (while cert valid 90) but after 80, for example, additional 20 days delay for each request will decrease total frequency.
3. Add additional IP and use it for part of...
Generating errors - can cause additional load, better to make your user fix error than rotate error-logs.
Also maybe it rotates once a day, even if it grows more than 32m
@zakazak because nowadays default zst format.
earlier pigz was compilled, then replaced by package from OS. Also some vps 1-4 cores may stuck if pigz will use few cores.
it's here, but not officially compatible with DA. they need to run more tests to announce it officially. But this didn't mean it will not work. So if you not hurry - you can wait 2-3 months till centos7 EOL and then jump to CL9.
@kke that's why important to keep system updated, your OS outdated too. Current Alma 8.9 yours 8.6
optimal scheme check for updates every week, at least every month.
in my CL8 and CL7 mariadb totally managed by CL and updates via YUM. Also it upgades via YUM and you need to upgrade mysql governor too to apropriate ver. it described on CL website/forum