Hi Kelsey, I've been using Let's Encrypt on my personal Evergreen test server (https://demo.evergreener.net) for this past month or so. Prior to that, I used Let's Encrypt for some other test systems at my previous place of work.
The biggest issue I encountered initially was that my system wasn't resolving the reverse DNS properly for my site (it took a little time for all the DNS to populate properly). This caused the letsencrypt-auto to fail for me. I think I ended up installing an additional python package to get that working in addition to giving enough time for DNS to propagate. The test system I used was installed with Ubuntu 14.04 server and apache 2.4, which letsencrypt seemed to have better luck in handling automatically the apache replaces with apache 2.4 vs. 2.2 (which shipped on older Ubuntu distros). Alternatively, I think I also just eventually figured out how to setup my eg.conf config file with the necessary paths for the SSL cert and chain files. Feel free to ask further questions about your issues. I think using Let's Encrypt is an awesome solution for SSL certificates. -- Ben On Sun, Mar 6, 2016 at 8:50 PM, Kelsey Lied <[email protected]> wrote: > Hi, > > I am wondering if anybody is using Let's Encrypt (letsencrypt.org) for their > Evergreen install. > > We're spinning up a new install and would like to use it, but so far I have > had no luck on our test server. I have tried a number of things, getting > various errors. The Let's Encrypt community has generally had an answer for > each error, but every answer I've tried messes with config settings that > ultimately prevent Evergreen from running properly. (Happy to provide > errors if folks are interested, but they're errors in another tool, so don't > want to bog down the initial query.) > > Is anybody using Let's Encrypt successfully? > > Thanks, > Kelsey
