• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Collabora in Docker Container

I remember it was pretty painful to deploy collabora with docker and nginx because it require to use a subdomain for collabora, then to add it in nextcloud.
I'm not sure if it's possible with Plesk because docker proxy rules are great for a simple container, but with additional directives it will be harder.
 
I'm using Plesk Onyx. The operation method may be different from the old version.
I first made a rule with the Proxy rule in the Website and Domain setting. And I confirmed the conf file created by Plesk. Based on that, I wrote it in the additional directive in the Apache and nginx settings. Then disable the proxy rule. But still I was unable to successfully start Collabora.
Next I changed Collabora part to Apache instead of nginx. Nextcloud site is nginx. In this case Collabora's launch went further. Displaying the initializing icon has finished and the warning error dialog box has been displayed. "Unauthorized WOPI host. Please try again later and report to your administrator if the issue persists." This error seems to be caused by an error in specifying the URL, but I specify the nextcloud server as well as the Docker container.
Is this method itself wrong? Nextcloud has set nginx, Collabora site as Apache. But the Collabora site seems to be using nginx instead of Apache. The vhost setting for Apache is completely ignored, and the nginx conf file is read.

Is this a proxy writing problem? Is the URL specification of the proxy incorrect? Will I add some additional processing?

collabora-error.jpg
 
Last edited:
Update 1.3.2 still in development stage. I have no any ETA of release.
 
I run collabora with this command.

docker run -t -d -p 127.0.0.1:9980:9980 -e 'domain=cloud.domain.tld\|domain2.tld' --restart always --cap-add MKNOD collabora/code

I think the problem is collabora needs lower case characters and docker over Plesk needs upper-case characters.

Gesendet von meinem G8341 mit Tapatalk
 
Hello Guys,

I have managed to run collabora on Plesk Onyx :

Here the docker run command :
Code:
docker run -t -d -p 127.0.0.1:9980:9980 -e "domain=your\\.nextcloud\\.tld" \
-e "username=admin" -e "password=admin" --restart always --cap-add MKNOD collabora/code

Where your\\.nextcloud\\.tld is your nextcloud instance address.

And here the additional nginx configuration I have used to setup my Nginx reverse-proxy for collabora :

Code:
        # 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;
    }

If you have an error message, try to restart docker service, with
Code:
service docker restart
or
Code:
systemctl restart docker
 
Last edited:
May i ask what nginx file you add that into ? is it just added to the nginx.conf for that domain ? bellow whatever is inside the config already.
 
in case someone is wondering . i added this to website & domain - apache & nqinx setting and at the bottom you can extra directives . that's where i added the above code and it worked ;)
 
in case someone is wondering . i added this to website & domain - apache & nqinx setting and at the bottom you can extra directives . that's where i added the above code and it worked ;)

Yes, the configuration I have previously posted can be added directly from the Plesk interface in the additonal Nginx directives block.
 
Back
Top