You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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)
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?
The text was updated successfully, but these errors were encountered: