-
Steps to reproduce
Expected behaviorCertificate should validate correctly. Actual behaviorCertificate is said to be invalid. Host OSWindows Server 2019. Nextcloud AIO version7.7.1 Current channelNot sure. Image is nextcloud/all-in-one:latest, so latest ? Other valuable infoI've tried following the steps in this bug here to no avail, since I cannot find What I triedI've tried using
Attemps
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
Hi, see https://github.com/nextcloud/all-in-one/blob/main/local-instance.md |
Beta Was this translation helpful? Give feedback.
-
@webmilio Where did you put what certificates? I currently run into the same issue where i get the local issuer error when my reverse proxy is pointing to 11000. In my reverse proxy i configured the certificate of my own domain, which nextcloud doesn't seem to like. I can't put it in the domaincheck-container because it's alpine and i haven't yet figured out how to do the equivalent of "update-ca-certificates". Altough i just checked the file you linked and it contains my Root CA. |
Beta Was this translation helpful? Give feedback.
I've just tried changing theAPACHE_PORT
to5001
and accessing the AIO interface locally instead of via the domain. I've changed my reverse proxy to point to theAPACHE_PORT
port as well, nothing changed.Restarted from complete scratch, followed all steps without modifying much of anything for Windows and reverse proxy. Same error. Trying to access said website via https://nc-domain:8443 gives me