Nextcloud Office (Collabora) is not able to establish a connection

Support apps
, ,
1

What app is this about, and its version: Nextcloud 34.0.1 & Collabora 26.04.2.2
What YunoHost version are you running: 12.1.40.1
What type of hardware are you using: VPS bought online

Describe your issue

Hi.
After the last Nextcloud update, Nextcloud Office (Collabora) is not able to establish a connection to my Collabora Online Server anymore.
Is there anybody who can help me?

On demand I share every log you wish to inspect.

Thanks a lot!

Share relevant logs or error messages

https://paste.yunohost.org/raw/idigudegek
https://paste.yunohost.org/raw/icuhenopox

2

Something related to collabora in nextcloud>admin>logging?
You can also check, via yunohost webadmin, collabora logs: tools>services>coolwsd.

3

Thanks for your reaction.

The protocol of Nextcloud is 25,5 MB big.
Here is the protocol of the service coolwsd:

Thank you for help.

4

Can you share the output of

df -h
journalctl -k | grep -iE 'oom|killed'

?

5

Hello.

This ist the output of df -h:

df_-h
df_-h555×184 24.7 KB

There is no output of journalctl -k | grep -iE ‘oom|killed’.

6

Same with me. “Use your own server” is greyed out. Previously I used the Yunohost Collabora server which I have removed now. I wanted to use an external instance, but I cannot change the server address

journalctl -k | grep -iE ‘oom|killed’ gives no output

I see this error in the nextcloud logs

simplexml_load_string(): -85ce-a2c04fa75dee",buildAssetsDir:"/assets/",cdnURL:""}}</script></body></html> at /var/www/nextcloud/apps/richdocuments/lib/WOPI/Parser.php#40

7

Maybe trying to uninstall and reinstall the nextcloud office app.

8

tried it, but did not help, I cannot edit anything

9

Please share logs and error messages.
I guess you will need to declare your nextcloud server as WOPI host in your collabora server configuration.

10

Try restarting coolwsd service.

tail -n 100 /var/log/nextcloud/nextcloud.log

And collabora service log after restarting.

11

Sorry. I did not have enough time the last days.

That’s the nextcloud-log:
nextcloud_log.pdf (346.3 KB)

And that’s the coolwsd-log:

Meanwhile I activated the Bulit-In-CODE-Server. It’s running and it works.

What I tried before:

I tried to reinstall (office.patronit.eu, patronit.eu/nextcloud, password, microsoft fonts) but get the message: “The service coolwsd didn’t fully execute the action start before the timeout.”

So I ran the following commands - that’s what’s ai and net research suggest:

sudo -i
yunohost app install collabora --no-remove-on-failure
sudo systemctl daemon-reload
sudo coolconfig set ssl.enable false
sudo coolconfig set ssl.termination true
sudo coolconfig set net.proto IPv4
sudo coolconfig set net.listen 127.0.0.1
sudo nano /etc/coolwsd/coolwsd.xml
sudo systemctl daemon-reload
sudo lsof -i :9980
sudo kill 31187 (the coolwsd process)
sudo systemctl daemon-reload
sudo chmod 644 /etc/coolwsd/coolwsd.xml
sudo mkdir -p /etc/systemd/system/coolwsd.service.d
echo -e “[Service]\nTimeoutStartSec=180” | sudo tee /etc/systemd/system/coolwsd.service.d/startup-timeout.conf
sudo systemctl edit coolwsd.service:

[Service]
TimeoutStartSec=180
Type=simple

sudo systemctl daemon-reload
sudo systemctl restart coolwsd
sudo systemctl status coolwsd

… ended in a nextcloud message:
”Failed to connect to the remote server: Server error: GET https://office.patronit.eu/hosting/discovery resulted in a 502 Bad Gateway response: 502 Bad Gateway body { width: 35em; margin: 0 a (truncated…)”