Nick Muerdter

@Energy1190: Thanks so much for the contribution and pull request! This will be great functionality to have! I'll try to take a closer look at the code this weekend. @Eihrister:...

@Energy1190: Apologies for my delayed response on this. Thanks for making the various changes, though! Since this is a more significant change, I'd still like to mull this over a...

Thanks all. I'll try to review and release this weekend. Sorry for the delay!

@fititnt: Sorry for the long delay and lack of response! I'll try to review this soon, but many thanks for your contributions!

@arturmkrtchyan: Sorry for the delay, but sure, a pull request would be welcome! Give a shout if you have any questions.

What version of lua-resty-auto-ssl are you running? And have you manually created or modified any of the files inside `/etc/resty-auto-ssl/letsencrypt/`? It looks the dehydrated Let's Encrypt client is failing during...

@tpimh: Try prefixing the socket path with `unix:`, so: `{ socket = "unix:/var/run/redis/redis.sock" }`. Assuming that does the trick, then I've hopefully clarified our docs about this (since this wasn't...

It should be possible to implement something like this with a custom `allow_domain` method and integrating it with [lua-resty-dns](https://github.com/openresty/lua-resty-dns) ([lua-resty-dns-cache](https://github.com/hamishforbes/lua-resty-dns-cache) may also be useful in this case). I can definitely...

@waynerobinson: Thanks for contributing this example! I'll try to give this a spin at some point and add in the README. Or if anyone else gets a chance to test...

I don't think I've seen this before. Based on where that's failing, that seems mostly to be happening on dehydrated's side with the request it's making to issue the cert....