# Nextcloud AIO logs wont be parsed

**URL:** <https://discourse.crowdsec.net/t/nextcloud-aio-logs-wont-be-parsed/1869>\
**Category:** Uncategorized\
**Created:** [June 12, 2024, 4:16pm UTC](https://discourse.crowdsec.net/t/nextcloud-aio-logs-wont-be-parsed/1869 "2024-06-12T16:16:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![semaf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/semaf/32/845_2.png) [@semaf](https://discourse.crowdsec.net/u/semaf)\
**Post date:** [June 12, 2024, 4:16pm UTC](https://discourse.crowdsec.net/t/nextcloud-aio-logs-wont-be-parsed/1869/1 "2024-06-12T16:16:18Z")

</div>

Hey,

Trying to setup crowdsec for Nextcloud AIO ([GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.](https://github.com/nextcloud/all-in-one)) where the access log is saved on host `/var/lib/docker/volumes/nextcloud_aio_nextcloud/_data/data/nextcloud.log` which is owned by www-data.

I set to acquis.yaml but nothing is going to be parsed. Maybe because the directory is accessable to www-data?

```auto
---
filenames:
 - /var/lib/docker/volumes/nextcloud_aio_nextcloud/_data/data/nextcloud.log
labels:
  type: Nextcloud
---

```

---

<div class="post-metadata">

**Author:** ![iiAmLoz](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/iiamloz/32/386_2.png) [@iiAmLoz](https://discourse.crowdsec.net/u/iiAmLoz)\
**Post date:** [June 13, 2024, 7:59am UTC](https://discourse.crowdsec.net/t/nextcloud-aio-logs-wont-be-parsed/1869/2 "2024-06-13T07:59:33Z")

</div>

Where is CrowdSec running on the host in a container or on the host itself?

typically the CrowdSec runs as root so permissions shouldn’t be an issue

edit: I saw this was also raised on [nextcloud discourse](https://help.nextcloud.com/t/nextcloud-aio-crowdsec-cant-parse/195001/2) from the acquisition I can see it most likely a host installation. Could you check `/var/log/crowdsec.log` and see if it mentions that it finds the file?