Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: LetsEncrypt! #298

Open
Meatballs1 opened this issue May 3, 2016 · 5 comments
Open

Feature Request: LetsEncrypt! #298

Meatballs1 opened this issue May 3, 2016 · 5 comments

Comments

@Meatballs1
Copy link
Contributor

Would be nice :)

@zeknox
Copy link
Member

zeknox commented May 3, 2016

The challenge with this one is the letsencrypt client typically requires that you disable all web services. This would require the process to stop apache, obtain the certificate, and then restart apache after a successful completion.

This would cause a downtime to any existing campaigns while obtaining the new certificate. Any workarounds that you're aware of to mitigate this?

@Meatballs1
Copy link
Contributor Author

I think there is an apache module for it :)

@Meatballs1
Copy link
Contributor Author

It looks like there are a couple of gems as well that help you do it too

@zeknox
Copy link
Member

zeknox commented Sep 20, 2016

@m1guelpiedrafita thats a really good find. I think it may work if we can dynamically change the configuration file that letsencrypt looks for it may suffice.

@zeknox zeknox added the Low label Nov 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
@Meatballs1 @zeknox and others