Nextcloud AIO Collabora Server Audit

[muzicman0]

Support intro

Sorry to hear you’re facing problems.

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

• Official documentation (searchable and regularly updated)
• How to topics and FAQs
• Forum search

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.

The Basics

• Nextcloud Server version (e.g., 29.x.x):
  • 32.0.1
• Operating system and version (e.g., Ubuntu 24.04):
  • Ubuntu 24.04
• Web server and version (e.g, Apache 2.4.25):
  • AIO
• Reverse proxy and version _(e.g. nginx 1.27.2)
  • Caddy (separate server)
• PHP version (e.g, 8.3):
  • AIO
• Is this the first time you’ve seen this error? (Yes / No):
  • yes
• When did this problem seem to first start?
  • since install
• Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
  • AIO
• Are you using CloudfIare, mod_security, or similar? (Yes / No)
  • no

Summary of the issue you are facing:

[…]

Steps to replicate it (hint: details matter!):

1. Open a document in Collabora

When I open a document in Collabora (using the one included in AIO) I get a notice to “Check the security warnings of your server.”.

When I do, I get the following:

I have not found a solution to solve this. Any ideas?

My Caddy block looks like this if it matters (and it is on a different VM, IP: 10.3.0.252 if it matters):

next.mydomain.com {
import logging nextcloud-aio
reverse_proxy 10.3.0.249:11000 {
header_up Host {http.reverse_proxy.upstream.hostport}
header_up X-Forwarded-Host {host}
}
# Handle WebDAV redirects for CardDAV and CalDAV
redir /.well-known/carddav /remote.php/dav 301
redir /.well-known/caldav /remote.php/dav 301
}

[scubamuc]

Hey @muzicman0 your post is a duplicate, see

collabora server security Alerts

Support intro Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. The Basics Nextcloud Server version (e.g., 29.x.x): replace me Operating system and version (e.g., Ubuntu 24.04): replace me Web server and version (e.g, Apache 2.4.25): replace me Reverse proxy and version _(e.g. nginx 1.27.2) replace me PHP version (e.g, 8.3): replace me Is this the first time you’ve seen this error? (Yes /…

[muzicman0]

Thanks. not sure how I missed that. I will post in that thread.

[scubamuc]

workaround and not a solution!

-- logging.disable_server_audit=true # enable disable server audit 

Collabora CODE for Nextcloud with Docker

Install & configure Collabora CODE for Nextcloud with Docker Collabora integration guide Collabora Online is a LibreOffice-based online office suite with collaborative editing, which supports all major documents, spreadsheet and presentation file formats and works together with all modern browsers. The Nextcloud Office integration app provides an interface for editing documents in Nextcloud with Collabora Online. Collabora CODE (Collabora Office Development Edition) is the development version…

[muzicman0]

@scubamuc

-- logging.disable_server_audit=true # enable disable server audit

I don’t know what this means? Where is that configuration applied? From my searching it seems that editing the coolwsd.xml file isn’t possible, but maybe that is wrong info?

Installing a different server doesn’t seem to work either. I tried to repurpose my previous VM that was dedicated Collabora server with the new AIO install, but that was a disaster.

Hopefully there is a way to either suppress or fix these errors.

[scubamuc]

@muzicman0

I don’t know what this means? Where is that configuration applied? From my searching it seems that editing the coolwsd.xml file isn’t possible, but maybe that is wrong info?

you use AIO?
you have a docker file?

you can add this as an environment variable in your docker compose. this is a workaround not a solution.

[scubamuc]

the only option is to work around this (at least for now) is via a separate Collabora server since the variable cannot be applied to the AIO mastercontainer compose file it seems

this message has no fundamental impact on functionality or limits use in any way and the popup window disappears after 3-5 seconds

[scubamuc]

Hey @muzicman0,

this issue will be fixed in AIO v12… its in the beta channel at the moment!

[muzicman0]

Great. Thanks. Since this will be my first update (when it is released), I will have to look into how to update the containers. I assume stop, prune, restart, but I will do some searching to see.

[vawaver]

It is very simple.
You can check my short tutorial here.

Nextcloud AIO v10.1.1 - Apache Will Not Start

I have updated my Nextcloud AIO to v.10.1.1 few minutes ago and let me share my experience how to solve some troubles. Here’s how I typically update my Nextcloud AIO setup, along with some tips to handle potential issues during the process. Stopping and Recreating Containers: I start by using the local Nextcloud AIO interface to stop all containers. Then, I log into Portainer and delete all stopped containers except for the mastercontainer. After deleting the containers, I allow the system …

Or if you want to read an advanced tutorial - find part 9. Troubleshooting & Updating Nextcloud AIO

Proxmox + NGINX + Nextcloud AIO + Watchtower Deployment Guide

1. Introduction This guide is designed for self-hosting enthusiasts who want to deploy Nextcloud AIO on their own infrastructure rather than relying on third-party hosting providers. It assumes that the user already has access to the following: a public IP address, a registered subdomain, and a running Proxmox server. While the guide primarily focuses on a Proxmox-based home or lab environment, it can also be adapted for VPS installations, provided certain conditions are met. Throu…

[muzicman0]

Thanks! I don’t have a UI (Ubuntu Server), so I don’t think I can use Portainer, but I imagine I can figure out the basics from what you have listed.

[vawaver]

@muzicman0

Operating system and version (e.g., Ubuntu 24.04):

• Ubuntu 24.04

Did you mean you’re using Ubuntu desktop?
It doesn’t matter if it’s Ubuntu server or desktop.

[muzicman0]

there is no desktop UI, just command line for my Ubuntu. When I searched Portainer (cuz I wasn’t sure what it was!!), it looked like a UI to manage docker. maybe that was wrong?

[vawaver]

Yes, it is a convenient tool for working with docker via GUI.

You can find many tutorials on YouTube on how to work with it. In 10 minutes everything will be clear to you.

But we are going offtopic.

[bb77]

@muzicman0

Hopefully there is a way to either suppress or fix these errors.

As this message is only shown to admin users, the most obvious way to suppress it without making any configuration changes would be to not use an admin account for day-to-day usage. This is also generally considered to be best security practice, aka the principle of least privilege.