Closed mm-ruhri closed 2 years ago
At least for some domains secured by letsencrypt, the image no longer is able to receive a token, due to certificate failure in start.sh in this line:
TOKEN_JSON=$(curl -d "username=$USERNAME" -d "password=$PASSWORD" {SERVER_URL}:${SERVER_PORT}/api2/auth-token/ 2> /dev/null)
An update to a newer debian release should help.
I don't know why, but since some weeks, some older versions of curl other used by curl ssl-libs are no longer able to verify certs and report them as invalid.
to problem exists not only in curl but also in the seafile-client which needs an update...
At least for some domains secured by letsencrypt, the image no longer is able to receive a token, due to certificate failure in start.sh in this line:
TOKEN_JSON=$(curl -d "username=$USERNAME" -d "password=$PASSWORD" {SERVER_URL}:${SERVER_PORT}/api2/auth-token/ 2> /dev/null)
An update to a newer debian release should help.
I don't know why, but since some weeks, some older versions of curl other used by curl ssl-libs are no longer able to verify certs and report them as invalid.