Nextcloud Collabora Problem

ℹ️ Support 📄 Office
,
1

Hello everyone,
I have the following problem, Nextcloud AIO loses Collabora without errors in the protocol, I can no longer access my write.
If I stop the containers in the interface and load them again, it will probably work again until the backup UTC 22:00, after which it won’t work anymore.
My installation: Nextcloud AIO 27.1.2; Nginx proxy manager
Does anyone have an idea which log file I can look in?

I found this one

Ready to accept connections on port 9980.

wsd-00001-00001 2023-09-21 12:36:15.592531 +0000 [ coolwsd ] TRC  Have 1 new children.| wsd/COOLWSD.cpp:5901
wsd-00001-00001 2023-09-21 12:36:15.592578 +0000 [ coolwsd ] INF  WSD initialization complete: setting log-level to [warning] as configured.| wsd/COOLWSD.cpp:5917
wsd-00001-00001 2023-09-21 12:36:15.593310 +0000 [ coolwsd ] ERR  #24: Failed setsockopt TCP_NODELAY: Socket operation on non-socket (ENOTSOCK: Socket operation on non-socket)| net/Socket.hpp:206
wsd-00001-00001 2023-09-21 12:36:15.593413 +0000 [ coolwsd ] WRN  Waking up dead poll thread [main], started: false, finished: false| net/Socket.hpp:704

hello@all
The following problem: Nextcloud AIO in the reverse proxy Nginx Proxy Manager (NPM) starts great, everything works fine
Collabora executable after daily backup Collabora no longer works. I found out
that it is not the backup but rather the forced shutdown of the Fritzbox around 3:00 a.m
I created a new public IP that also applies to both DynDns (cloud.xxxxx.tld and collabora.xxxxxx.tld)
to get redirected. Collabora works again when I add the public IP to the Allow list for WOPI requests add.
How can I change this so that the Dyndns take over tld’s? Or it works automatically.

Nextcloud AIO runs on Ubuntu VM 23.04 Docker Container Proxmox Server IP:192.168.xxx.156
Nginx NPM also runs on Ubuntu VM 23.04 Docker Container Proxmox Sever IP:192.168.xxx.168

separate VMs, Fritzbox release https and http

Collabora also runs on the Nginx server and was integrated like this:

docker run -t -d -p 9980:9980 -e “domain=cloud\.xxxxxx\.tld” --name=COLLABORAOFFICE --restart always --cap-add MKNOD collabora/code
####### Nginx Proxy Manager config #######

  1. Create your new Proxy Host, specify https protocol and the server host/ip and port 9980 (192.168.xxx.168:9980). Also enable Websockets Support.
  2. On the SSL tab select a new certificate, enable HTTP/2.
  3. On the Advanced tab, enter:

# static files
location ^~ /loleaflet {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# WOPI discovery URL
location ^~ /hosting/discovery {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# main websocket
location ~ ^/lool/(.*)/ws$ {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

# download, presentation and image upload
location ~ ^/lool {
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
}

# Admin Console websocket
location ^~ /lool/adminws {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

Greetings Werner

2

Your post is very confusing to me. On the one hand, you describe your existing problem in English, and on the other hand, you post some article in German below it, but you don’t tell me in which context it is related to your explanations. Thus a goal-directed assistance is impossible. I expect a little more effort, if you expect help from others!

Therefore, I do not want to go into detail about the text. But what I noticed at a glance are the errors in the posted proxy configuration. If this looks the same for you, there can be no communication between Collabora and Nextcloud! Collabora changed the path names some time ago. The proxy configuration still has the old ones. So “loleaflet” must be replaced by “browser” and “lool” by “cool”.

I can’t say anything about the actual Nginx config, because I only use Apache.

3

sorry, that was the devil’s mistake :-))
And thanks for your tip, I’ll revise the script and see if it works.

4

Hi Werner re-reading your post makes me somewhat clueless… you are using aio but at the same time your run separate collabora-online container.

Assuming you don’t use AiO integrated CODE you should follow this guide: Nextcloud Collabora integration - it will give you good guidance to troubleshoot the installation

In case you are trying to get aio working you better review the installation and start following AiO behind reverse proxy guide

1 Like