Troubleshooting guide

Paperless-ngx File Path Not Found: Fix the Watched Import Volume

Category: Document Workflow

You placed files in the watched import folder, but Paperless-ngx ignores them and logs a path error, leaving you stuck before diagnosis.

Confirm the container sees the path

Open a shell in the Paperless-ngx container and list the watched folder exactly as configured. If the path does not exist, the volume mount is wrong. Check your Docker Compose or run command for the host-to-container mapping. The container path must match the consume directory setting. A common mistake is mounting to /usr/src/paperless/consume while the app expects /consume, or vice versa. Run docker exec -it paperless-ngx ls -la /your/consume/path. If you see “No such file or directory,” fix the mount and restart the container.

Check permissions and ownership

Even if the path exists, the paperless user must read and write there. List the folder and note the owner and mode. If it is owned by root with no write permission for others, files will be ignored. Adjust ownership on the host to match the container user (often UID 1000) and restart. This step often reveals a paperless ngx file path not found condition caused by a missing or misnamed mount.

Verify the consume configuration

In the admin interface, confirm the consume directory setting points to the same path you mounted. A trailing slash or typo will cause a path not found error. Save and restart the container after any change.

Verification test

Place a small text file in the watched folder. Watch the container logs for consumption messages. Within a minute, the file should disappear from the folder and appear in Paperless-ngx. If it remains, recheck the mount and permissions.

Rollback note

If a configuration change breaks startup, revert to your previous Compose file and restart. Keep a backup of working settings before editing.

If the path still fails after these checks,

A scanned document and Paperless-ngx search result on a laptop

Ask for help.


Back to the service page · Ask about this exact symptom