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 Sep 2, 2021. It is now read-only.
Some users are migrating existing certificates in to RP, and these certs may not be named in the way that we expect (fullchain, privkey). Also, some containers may actually use these certificates internally and expect them to be named in certain ways.
RP should have labels to specify custom certificate names.
The text was updated successfully, but these errors were encountered:
When you use other names than acmetool provides RP is not able to renew those certificates. I don't know if this is something we really want?
Also imho - RP is an SSL-Termination Proxy so if an container itself needs an functional ssl-cert it would be better to proxy the ssl-request to it and this can be achieved with the vhost.d config files or am i wrong?
Some users are migrating existing certificates in to RP, and these certs may not be named in the way that we expect (fullchain, privkey). Also, some containers may actually use these certificates internally and expect them to be named in certain ways.
RP should have labels to specify custom certificate names.
The text was updated successfully, but these errors were encountered: