Errors while trying to open a document

User Support
2

Troubleshooting Steps

  1. Check Permissions:

    • Ensure that the /opt/cool/systemplate directory and its contents have the correct permissions set so that the Collabora service can read/write to it.
    • You can change the permissions with commands like:
      sudo chmod -R 755 /opt/cool/systemplate
sudo chown -R <user>:<group> /opt/cool/systemplate
    • Replace <user> and <group> with the appropriate values for your setup.

  2. Update Systemplate Files:

    • Since the logs indicate that files in /opt/cool/systemplate/etc are out-of-date, consider copying the updated systemplate files. This typically involves running a command to sync the configuration files if you haven’t already.

  3. Verify WOPI Configuration:

    • Make sure that the WOPI endpoint URL configured in Collabora matches the actual URL your Nextcloud installation is using. Check your Collabora configuration file for settings like:
      <server>
  <url>https://cloud.DOMAINNAME.TLD</url>
</server>
    • Additionally, ensure that the WOPI URL has the correct access tokens set up and that the Collabora server can communicate with the Nextcloud server.

  4. Review Docker Capabilities:

    • If you’re running Collabora in a Docker container, you might need to provide additional capabilities, such as --cap-add=CAP_CHOWN, to allow the container to change ownership of files. Adjust your Docker run command accordingly:
      docker run --cap-add=CAP_CHOWN ...

  5. Check Network Configuration:

    • Ensure that there are no network issues preventing the Collabora server from reaching the WOPI endpoint. You can test this by accessing the WOPI URL directly in a browser to see if it returns the expected response.

  6. Log Review:

    • Continuously monitor the Collabora logs after making adjustments to capture any new errors or warnings that may help further diagnose the problem.

  7. Reboot the Service:

    • After making the above changes, restart your Collabora service to ensure all configurations are reloaded correctly:
      sudo systemctl restart coolwsd

Thanks,
Darshan