Siwat2545

That should not be what show up. It should be the "Document Server is running" page. I don't use SWAG so I can't help you there so you should ask in the proxy's support thread.

what happens when you visit the url using chrome?

only change to http in nginx configuration. Here's what it's doing, nextcloud make a https request to nginx, nginx forward that to document server with http. so nextcloud still see the server as https.

try proxy_pass to http instead of https

So I umount the disks then stop mdadm then yeet the plug. Formatting went fine, running correcting parity-check right now

It been 30 minutes already Here's the diagnosis Ignore the CRC error, I already tried replacing the cable, it doesn't go away. mainserver-diagnostics-20210629-0903.zip

when you edit the container, what is in your ‘repository’ field?

Since I only ported the official container, I do not know the inner working of these logs, I suggest that you ask here https://dev.onlyoffice.org/viewforum.php?f=4&sid=c5c0ec08795675163814c27b1f6577be

What seem to be the problem, does the web ui does not show up?

NVM, I confused HSTS with CORS, I don’t really know how to solve this as I do not use NGINX based reverse-proxy, but I heard that people got it working when DS have the correct certificates (in Data/certs directory)

What you just post there is called the server block, can I see one for the onlyofficeds? it should have a directive "server_name onlyoffice.MYDOMAIN.com"

That suggest that the certificate is not wildcarded at the sub domain level

In my setup, I use one wildcard certificate that cover both nextcloud and onlyoffice install. maybe you can try that?

The problem is probably with your reverse proxy, the two will refuse to talk if the certificate does not match. I don't really know how gui get change in to conf, do you happen to have an nginx server block for onlyoffice?