certbot renew will attempt to renew all certs in one pass and if you use a --deploy-hook you can initiate the single apache reload (and it will only execute whenever a cert is actually renewed).
When - use the --deply-hook parameter, all ( almost ) expired certificates will be renewed without an apache reload after each renewal? Only an apache reload at the end configured in the --deploy-hook ?
What authenticator and/or installer plugin is used? The apache plugin requires reloads for the authentication and/or installation tasks. Unfortunately, all the certificates use a “separate” instance of the plugin, so every cert will separately reload twice (or even thrice).
Using a hook will not tell the apache plugin not to reload. The reloading is required and the plugin doesn’t “pool” all the authentications or certs to minimise the reloading.
It’s the apache plugin. So what you are saying is that every single renewal will force an Apache reload? So when i have 30 sites and 30 almost expired sites, Apache will reload 30 times or more?
Yes, as far as I know, that indeed is the case. However, a reload shouldn't be thát problematic?
An alternative is not using an installer plugin, use the certonly mode with the webroot plugin, install the certificate manually and use the --deploy-hook as mentioned above.
a single reload is working perfectly. But on my server, i serve several sites (500) which are hosted on several backend servers, its problematic . Apache is only the frontend serving SSL and is the LoadBalancer. After 30 renews, apache stopped reloading. When is take a look into the processes on Linux is noticed that Apache was completely unloaded. I have to reboot the entire server to start Apache again.