Closed mmmint closed 5 years ago
Found it!
It was inside the Dockerfile
and therefore in the built docker image:
HEALTHCHECK --interval=30s --retries=3 CMD curl --fail http://localhost:5232 || exit 1
This won't work as SSL is active and therefore HTTPS is used instead, bringing with it a pollution of misleading errors in the logs.
Executing the curl
command inside the container using the argument --insecure
or -k
for self-signed SSL certificates.:
/ # curl --fail --insecure http://localhost:5232
curl: (52) Empty reply from server
/ # curl --fail --insecure https://localhost:5232
Redirected to .web/ #
/ # echo $?
0
The question is how to implement the HEALTHCHECK
so that it works when SSL is enabled, as well as when it's disabled....
Something like this (round brackets are just used for the sake of clarity)..?
( curl --fail http://localhost:5232 || curl --insecure https://localhost:5232 ) || exit 1
See #44 for a way to override the healthcheck:
--health-cmd='curl --fail https://localhost:5232 || exit 1' --health-retries=3 --health-interval=30s
Hello guys, Hopefully you can help me further... I was using a self-signed certificate and everything was working fine until yesterday. Now Im getting following error:
I generated both key and certificate with
openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout radicale.key.pem -out radicale.cert.pem
. Here the radicale config: