3 ms·
1. The certbot client is not a product of the Let's Encrypt CA and is not mandatory. You can use another client. 2. With the certbot client, instead of using a
by wolf550e 7y ago
1. The certbot client is not a product of the Let's Encrypt CA and is not mandatory. You can use another client.
2. With the certbot client, instead of using a deep integration with your http server, you can use `certbot certonly --webroot --webroot-path /var/www/html/.well-known/ -d example.com` (or similar) and provided you told your web server to serve file from the /var/www/html/.well-known/ filesystem directory under the /.well-known/ url path prefix on your domain, cert issuance and renewal will work. This should be easy to do with any web server. certbot will not know which web server you happen to use and will not care. You can replace the web server and renewal will keep working.