-
Steps to reproduce
Actual behaviorI configured nextcloud all in one with the following environment variable, pointing to a folder containing my CA: As a result, the CA was successfully mounted and accepted by nextcloud container: docker exec -it nextcloud-aio-nextcloud ls -l /usr/local/share/ca-certificates/
total 4
-rw-r--r-- 1 1000 1000 1025 May 15 13:18 root-ca.crtBut not mounted in the notify-push container: > docker exec -it nextcloud-aio-notify-push ls -l /usr/local/share/ca-certificates/
total 0Making it fail to connect back to nextcloud with the following error (loop): Expected behaviorI was expecting notify-push container to also trust my CA, and successfully connect to nextcloud. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi, generally AIO does not support self-signed certs: https://github.com/nextcloud/all-in-one#are-self-signed-certificates-supported-for-nextcloud. https://github.com/nextcloud/all-in-one#how-to-trust-user-defined-certification-authorities-ca is mainy intended for connections from Nextcloud to the outside. However I'll accept a PR that also allows to mount the certs into the notify-push containers so that it can use that in there. I've also added this to #5251 in the meantime. |
Beta Was this translation helpful? Give feedback.
Hi, generally AIO does not support self-signed certs: https://github.com/nextcloud/all-in-one#are-self-signed-certificates-supported-for-nextcloud. https://github.com/nextcloud/all-in-one#how-to-trust-user-defined-certification-authorities-ca is mainy intended for connections from Nextcloud to the outside.
However I'll accept a PR that also allows to mount the certs into the notify-push containers so that it can use that in there. I've also added this to #5251 in the meantime.