• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Pesk Docker running collabora online for nextcloud

cij

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Version 18.0.61
Hello,

On a Ubuntu 22 server, I have installed Plesk and am also running the Docker engine. I have successfully installed Collabora Online and set up a subdomain. Additionally, I have configured the reverse proxy settings in Nginx, and everything seems to be working correctly. The subdomain is also connected with the docker on port 9980. This means that when I add the subdomain in the Nextcloud backend, the Collabora Docker version is accessible and recognized as the correct Docker version. On the Docker itself, I can also access the Collabora admin interface without any issues.

However, when I try to open a document inside Nextcloud, I get the following error message:

Loading the document failedThe socket connection could not be established or was unexpectedly closed. The reverse proxy might be misconfigured. Please contact the administrator. For more information on proxy configuration, visit Proxy settings — SDK https://sdk.collaboraonline.com/ documentation

It seems that I have made a mistake in the configuration. I have deactivated Apache for the subdomain and am running only Nginx with the following additional settings:


# static files
location ^~ /browser {
proxy_pass http://127.0.0.1:9980
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

# WOPI discovery URL
location ^~ /hosting/discovery {
proxy_pass http://127.0.0.1:9980
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

# Capabilities
location ^~ /hosting/capabilities {
proxy_pass http://127.0.0.1:9980
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

# main websocket
location ~ ^/cool/(.*)/ws$ {
proxy_pass http://127.0.0.1:9980
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 36000s;
}

# download, presentation and image upload
location ~ ^/(c|l)ool {
proxy_pass http://127.0.0.1:9980
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

# Admin Console websocket
location ^~ /cool/adminws {
proxy_pass http://127.0.0.1:9980
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 36000s;
}

I have tested a lot of different settings but get not running the setup. Maybee anyone can help with this issue?
 
Back
Top