-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
Container itself does not trust the Lets Encrypt certificate? #111
Comments
Is this not a duplicate of #106 ? |
No, the error in #106 can be solved by mounting volumes, so the letsencypt folders persists and https works. Without that config a certificate cannot be fetched at all. In My case then the issue specified above happens. |
I'm not an expert but most tomcat tutorials consider this message normal and can be safely disregarded. For example, https://www.geocerts.com/support/install-ssl-certificate-tomcat-server Can you please explain more what's expected? |
Indeed, but in that case the startup prompts for: ... is not trusted. Install reply anyway? [no]: and hangs there until you specify yes as answer. B |
If you know a solution let us know to integrate. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. See the FAQ for more information. |
Hi,
running the latest docker version and the Lets encrypt certificate is requested on every startup, additional on startup it prompts:
Any hint?
Thanks
docker run -it -m1g -v "/opt/docker/drawiodata/letsencrypt-log:/var/log/letsencrypt/" -v "/opt/docker/drawiodata/letsencrypt-etc:/etc/letsencrypt/" -v "/opt/docker/drawiodata/letsencrypt-lib:/var/lib/letsencrypt" -e LETS_ENCRYPT_ENABLED=true -e PUBLIC_DNS=xy.westeurope.cloudapp.azure.com -e DRAWIO_BASE_URL=https://xy.cloudapp.azure.com -e DRAWIO_MSGRAPH_CLIENT_ID=xx -e DRAWIO_MSGRAPH_CLIENT_SECRET=xx -e DRAWIO_MSGRAPH_TENANT_ID=xx --rm --name="drawio" -p 80:80 -p 443:8443 jgraph/drawio
Full log:
The text was updated successfully, but these errors were encountered: