I use the standalone server that comes with certbot along with a cron script to shut down ATS, run certbot, then restart ATS. Also not elegant but I could not get a redirect to work for this.
On Dec 5, 2016, Jered Floyd <[email protected]> wrote: > >Is anyone currently using ATS with Let's Encrypt as a certificate >provider? > >My current plan is to do something like: >1) Run Apache Server locally on a non-standard port (e.g. 8000) > >2) Add a rule mapping all access to /.well-known/acme-challenge/ to the >local server: >regex_map http://*/.well-known/acme-challenge/ >http://proxy-host.domain.com:8000/ > >3) Use certbot's "webroot" authenticator plugin to satisfy http-01 >challenge types > >4) Use certbot renew --post-hook to refresh ATS after certificate >renewal > > >This is relatively simple, but running another server locally feels >inelegant. I don't believe ATS can be configured to serve local file >system content, though. Any alternative suggestions I should explore? > >--Jered
