3 ms·
I stopped using Let's Encrypt when they broke Apache servers not using virtual hosting.
by Animats 7y ago
I stopped using Let's Encrypt when they broke Apache servers not using virtual hosting.
- oneplane 7y agoGood for you? I guess? Not sure what to do with that comment of yours. Is it an attempt at venting or constructing a situation where Let's Encrypt is responsible for your server?
- wolf550e 7y ago1. 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.
- vbezhenar 7y agoJust don't use auto stuff. Be responsible for your configuration. certbot certonly --webroot works fine.
- privateSFacct 7y agoCertbot is from EFF not let's encrypt - you can actually write your own certbot if it doesn't do what you want - nothing to do with lets encrypts. Lots of instructions for many common situations here: https://certbot.eff.org/all-instructions https://certbot.eff.org/all-instructions Did you check that you were running it with the right command flags? If certbot has a bug that breaks things in a situation it's intended for do file a bug or even better a patch to fix the bug.
- sschueller 7y agoYou can use dehydrated [1] which is a single shell script that you can trigger via cron to do the whole let's encrypt stuff for you. No dependancies other than curl. [1] https://github.com/lukas2511/dehydrated https://github.com/lukas2511/dehydrated