5 ms·
Surprised no one is commenting that their software has really poor usability. It may work well in providing secure certificates, but setup is a PITA and the doc
by sp527 10y ago
Surprised no one is commenting that their software has really poor usability. It may work well in providing secure certificates, but setup is a PITA and the documentation is abysmal.
- lucb1e 10y agoAgreed. If I remember correctly it even destroyed a site once when it was attempting to make sure their validator could reach the verification file. I just did what everyone said: "it's so easy, just run it on auto mode with apache and it'll configure your cert for you". Turned out to be a huge PITA. Recently I had to renew that site again (I've been postponing and dreading it) and looked for a different client. The getssl bash script[1] had its own problems (all caused by me not taking the time to read the readme, but the default settings were a bit odd), but overall a 10× better experience than the official client. Much less magic, much more a unix-like tool ("it does only one thing, and one thing very well"). [1] https://github.com/srvrco/getssl https://github.com/srvrco/getssl
- tghw 10y agoI'm not sure I like their "we'll do it all for you" approach. It seems like there are a lot of ways to accidentally break config files. In general, I'd rather not anyone touch those without me knowing what it will do. Fortunately, the certonly script grabs the cert and puts it in an easy location. Updating the config from there is easy enough.
- tghw 10y agoReally?? I found it dead simple to use. 1. Install the app. 2. Run the certonly script, following the prompts. 3. Point the server at the certificates. The only hitch was stopping Nginx long enough to do the domain verification. A three line bash script fixed that.
- niij 10y agoCheck out Lego [0]. You can do DNS verification instead, no need to restart nginx :) [0]: https://github.com/xenolf/lego https://github.com/xenolf/lego