Skip to content
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.

Automating renewal? #4

Open
mdeneen opened this issue Feb 23, 2020 · 3 comments
Open

Automating renewal? #4

mdeneen opened this issue Feb 23, 2020 · 3 comments

Comments

@mdeneen
Copy link

mdeneen commented Feb 23, 2020

First of all, I really like this method of renewing certificates and the acme v2 client works great. When something goes wrong, though, it can be a bit difficult to handle and you end up with unexpected output in the pem file.

I ran the curl command, validated the entries, and life was good. Five minutes later I ran the same command and it issued new certificates. This is something that will surely get me in trouble if I placed it in a cron job.

Is there a recommended practice here?

@anezirovic
Copy link
Contributor

Hello, thanks for reporting the usability issues, we probably want detect already issued certs, so it doesn't request for new cert every time you run the commands. For now, you'd need to check the cert file on disk yourself (with openssl command), and decide whether to request new cert.

  • There is some pending work with haproxy-lua-acme, since starting with HAProxy 2.1 we have option for handling certs (see CLI options like show ssl cert, set ssl cert, etc)

@github-tomster
Copy link

any news on that?

@ieugen
Copy link

ieugen commented Jan 7, 2022

Looking at this in 2022.
I wonder how hard would be to merge this functionality with hashicorp consul (via API) or hashicorp vault.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants