Ah you have NC on a valid domain and cert and OO on another domain but with a self-signed cert right? Then the warnings make sense. Mixed content. But I still do understand why this is an issue. I am using valid certs for the outside world in my reverse proxy and private ones for the internal hosts. As you know was a bumpy road yesterday
That’s right! So Nextcloud is accessible via the proxy where LetsEncrypt SSL terminates.
But, because OO is in the same vLAN as NC, there’s no need for NC to go out to the proxy and back into the network to access it; it connects directly, but as NC is accessed over HTTPS, OO needs to be HTTPS too, though as it’s not public the certs don’t need to be trusted.
I figured this would be enough, but I didn’t take into consideration the use of iFrames and Chrome inspecting the validity of the iFrame cert, so has led to this problem.
I imagine I’m not the first, nor last to run into this scenario, hence the PSA