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
For the hosts I am using nginx-proxy for, I want one of the hosts to use a cert generated outside of this LE companion container. My use case is I need a wildcard cert, which I have generated separately. Mounting this from the host to the container works great and I am using the CERT_NAME env var.
After some time, the custom cert files are removed, and I suspect this container is overwriting those files. Note the filename does not match any host that this container is configured for with a LETSENCRYPT_HOST env var. Custom files are removed, not overwritten.
Is it possible to use this container alongside custom certs on the same nginx-proxy container? If not, is there some sort of known workaround for this use case.
Thanks!
The text was updated successfully, but these errors were encountered:
After some time, the custom cert files are removed, and I suspect this container is overwriting those files. Note the filename does not match any host that this container is configured for with a LETSENCRYPT_HOST env var. Custom files are removed, not overwritten.
This should have been fixed recently (see #465 and #472).
Could you try again with an up to date version of the container ?
For the hosts I am using nginx-proxy for, I want one of the hosts to use a cert generated outside of this LE companion container. My use case is I need a wildcard cert, which I have generated separately. Mounting this from the host to the container works great and I am using the
CERT_NAME
env var.After some time, the custom cert files are removed, and I suspect this container is overwriting those files. Note the filename does not match any host that this container is configured for with a
LETSENCRYPT_HOST
env var. Custom files are removed, not overwritten.Is it possible to use this container alongside custom certs on the same nginx-proxy container? If not, is there some sort of known workaround for this use case.
Thanks!
The text was updated successfully, but these errors were encountered: