please test also:
1) revoke LE on a domain
2) enable LE on a domain after you revoke another domain
Pay attention to LetsEncrypt limits. Adding, revoking, adding again...
Better is to clearly say us what is not working, eg:
You cannot imagine how we lose time by trying to understand your posts (no specially your posts)
See https://community.letsencrypt.…its-for-lets-encrypt/6769
Revoke and recreation is working fine. We already tested... About step 2, domain1 has nothing to do with domain2. You create certificates for each domain + www.domain (for subdomains it would be subdomain + www.subdomain...).
So you want just that we test because of less trust or you found a problem?
BTW: We already tested x scenarios 
PluginManager added a new version:
QuoteVersion compatible with i-MSCP Serie 1.4.x, 1.5.x
CHANGELOG
- Fixed: Cron job for SSL certificates renewal abort due to missing bind variable (SQL statement)
- Fixed: Required distribution packages are not installed while plugin installation (regression fix)
- Review: Default policy for SSL certificate renewal (automation) now set to 21 days to fit with Let's Encrypt expiry notices
- Updated: Certbot from version 0.24.0 to version 0.26.1
PluginManager added a new version:
QuoteVersion compatible with i-MSCP Serie 1.4.x, 1.5.x
- Certbot client update to version 1.7.0
