Paperless Error [Errno 13] Permission denied: '/usr/src/paperless/consume

[markyman2975]

Hi@all,

sorry for my bad English i´m from german and have trouble...

I want to implement the following:
There are 2 VM: 1 Paperless
2: Nextcloud
In VM 1 I created an NFS share, integrated it into VM2 Nextcloud with external storage.
In Nextcloud the folders are called: PDF Input (with VM 1 folder:
/docker/paperlessngx/consume) and PDF Output ( with the folder /docker/paperlessngx/media/documents/archive.
If I now put a PDF in the VM 2 Nextcloud PDF Input folder, it should arrive paperless, be processed and then filed. Once filed, it will appear in the Nextcloud PDF-Output folder. Well, now it doesn't work. There are several problems:
1: Do I perform the authorization in the VM2 Nextcloud:
chown -c -R www-data:www-data /docker/paperlessngx/consume
chown -c -R www-data:www-data /docker/paperlessngx/media/documents/archive
then after a restart this permission is no longer there.
2. In Paperless I get the error message:
[Errno 13] Permission denied: '/usr/src/paperless/consume
So it seems to be a permissions issue as well. Can someone help??

[stumpylog]

If the consume directory is owned by www-data, you'd either need to run the container as that user or add more permissions to the folder allowing the paperless user to read and write from it

[markyman2975]

Hi,
that's exactly what I don't understand. www-data is owned by the 2 VM, i.e. Nextcloud. If Paperless reports an error then there must be a rights problem in VM 1, right? Here are the rights in VM 1:
-rw-r--r-- 1 root root 2708 Apr 22 16:38 wget-log

[ph1248]

In which way did you install paperless in VM1? Docker, or bare metal?

[markyman2975]

Docker, Portainer with docker Compose.yml

[ph1248]

Unfortunately I don't have any experience with docker.

Maybe this thread: #3155
can help you? The problem there seems possibly related.

[markyman2975]

Problem solved, the permission must be set.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.