Resolved Using Nextcloud and Collabora online with nginx

[Zoo3]

I'm trying to install Collabora now. The editing screen of Collabora is displayed, but it is in a state where it is impossible to open important data.

docker run -t -d -p 9980:9980 -e "domain=sample\\.domain\\.com" --cap-add MKNOD collabora/code

*This is the portion of 9980:9980.

When I create a container via Plesk's Docker UI, the console log of the container is displayed. However, when I create a container with SSH, the log isn't displayed.
But this is still a small problem. A bigger problem is that it doesn't work properly.

I made a container and set up nginx to complete the preparation. When I actually open the odt file, the screen changes to the screen of the office application. "Initialization in progress" is displayed momentarily. But data doesn't start.

I think the item value set with the additional directive is incorrect. Is there a way to know the location of the directory in the container?

 

[Zoo3]

Finally I was able to install and run. Try and error, it was a long way.
The cause was very simple.

It was "uppercase letters and lowercase letters" of the characters registered in the environment variable when Docker's container was created. It seems that this is important because environment variables are "lowercase letters". When I create a container and set up a container with Plesk UI, I modify the environment variable to capital letters. This is Plesk's specification. As a result, this was a problem. In other words, Collabora Online container should NOT be edited with Plesk.
Why did I not notice it? I restarted Docker, but didn't restart the server. It seems useless to restart Docker. I started using Collabora by restarting the server. I restarted not only Docker but also nginx and php-fpm. But these are ineffective. I needed to restart the server. I think there is also a lack of my knowledge.

1. docker run -t -d -p 9980:9980 -e 'domain=nextcloud_host\.domain\.com' --cap-add MKNOD collabora/code
2. Activate container.
   
3. <PLESK menu> Website and domain setting > Apache and nginx settings > Additional directives for nginx
4. Write a reverse proxy setting for nginx of Collabora here. *You probably need to adjust to your own environment.
   https://icewind.nl/entry/collabora-online/
5. Restart the server.
6. Designate the operation server of Collabora from the setting of nextcloud.

In my case I succeeded in this

 

[tobasium]

Hi,

I don't know to write the reverse proxy settings :

Ungültige nginx-Konfiguration: nginx: [emerg] unexpected end of file, expecting ";" or "}" in /var/www/vhosts/system/cloud.tobasium.de/conf/vhost_nginx.conf:43 nginx: configuration file /etc/nginx/nginx.conf test failed

server {
    listen       443 ssl;
    server_name  cloud.tobasium.de;

    ssl_certificate /usr/local/psa/var/modules/letsencrypt/etc/live/cloud.tobasium.de/;
    ssl_certificate_key /usr/local/psa/var/modules/letsencrypt/etc/live/cloud.tobasium.de/;

    # static files
    location ^~ /loleaflet {
        proxy_pass https://localhost:9980;
        proxy_set_header Host $http_host;
    }

    # WOPI discovery URL
    location ^~ /hosting/discovery {
        proxy_pass https://localhost:9980;
        proxy_set_header Host $http_host;
    }

   # main websocket
   location ~ ^/lool/(.*)/ws$ {
       proxy_pass https://localhost:9980;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "Upgrade";
       proxy_set_header Host $http_host;
       proxy_read_timeout 36000s;
   }

   # download, presentation and image upload
   location ~ ^/lool {
       proxy_pass https://localhost:9980;
       proxy_set_header Host $http_host;
   }

   # Admin Console websocket
   location ^~ /lool/adminws {
       proxy_pass https://localhost:9980;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "Upgrade";
       proxy_set_header Host $http_host;
       proxy_read_timeout 36000s;
   }
}