{"id":137,"date":"2025-07-20T12:15:13","date_gmt":"2025-07-20T11:15:13","guid":{"rendered":"https:\/\/david.lidstone.me\/blog\/?p=137"},"modified":"2025-07-26T12:32:39","modified_gmt":"2025-07-26T11:32:39","slug":"paperless-ngx-real-world-install","status":"publish","type":"post","link":"https:\/\/david.lidstone.me\/blog\/?p=137","title":{"rendered":"Paperless NGX Real World Install"},"content":{"rendered":"\n

What is Paperless NGX?<\/h2>\n\n\n\n

Paperless is a mature document management system with lots of features. NGX is the latest fork. I highly recommend it, but I won’t go into the features here – just search YouTube for some videos and there is lots of information.<\/p>\n\n\n\n

So, if there is lots of information, why would you want to follow this install? Because although there are lots of tutorials, most of them are focused on ‘fast’ and ‘easy’, and the upshot is something you can play around with, but would not want to rely on. The tutorials also don’t tend to go into the stack in much detail and can end up a bit “you know what to do”. I don’t. I really don’t.<\/p>\n\n\n\n

Having mainly been using containers (and having other reasons for keeping my single home-server on Windows) I don’t have a Linux server to use. I also want to use a NAS for the file storage as I don’t have a lot of room on my server. <\/p>\n\n\n\n

So, what are we doing?<\/h2>\n\n\n\n

A quick disclaimer before we dive in. I used perplexity.ai and ChatGPT heavily (and over many hours) to get this straight, so most credit goes to whomever it was stolen from by the AI.<\/p>\n\n\n\n

The stack will be:<\/p>\n\n\n\n

Windows 10 –> Hyper-V –>Ubuntu 24 LTS –> Docker<\/mark><\/p>\n\n\n\n

My Windows 10 is running on a Dell Optiplex 3050 (great as a small, cheap home server). I am also using an ASUS RT-AX86U with an external HD shared over Samba \/ CIFS for the NAS storage. If your NAS supports NFS instead, then I would recommend using that, but I won’t be covering it here.<\/p>\n\n\n\n

We’ll end up with a working install of Paperless NGX with the data folders mounted on the NAS and the GUI available on the local network. All functionality will work, including ingesting documents using the ‘consume’ folder and exporting (again, to the NAS).<\/p>\n\n\n\n

You could easily do the exports to another location, such as a second NAS or cloud storage, and also expose the GUI to the internet if you really wanted, but I prefer access over VPN. If you do want to expose the GUI, be aware that this install does not include setting up https.<\/p>\n\n\n\n

Why not just Docker Containers like the tutorials?<\/h2>\n\n\n\n

Well, I do use Docker on Windows 10 and WSL, however, I don’t suggest trying to get the mounts working properly as well as sharing the GUI on the LAN. Life is too short and the information that I could fine was dated, confusing, sometimes plain wrong and ultimately not that helpful. I even asked ChatGPT to help but it just laughed and told me not to waste its time. If anyone cracks this, then be a hero and let me know!<\/p>\n\n\n\n

The Build<\/h2>\n\n\n\n

Getting started with Hyper-V and Ubuntu<\/h3>\n\n\n\n

Install Hyper-V, if you don’t already have it. There are plenty of tutorials which will cover this.<\/p>\n\n\n\n

Next, download the ISO of Ubuntu Server<\/a>. I used 24.04.2 LTS.<\/p>\n\n\n\n

In Hyper-V, find the Virtual Switch Manager and create a new external switch associated with your network adapter. This is my added switch:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Create a new Virtual Machine (don’t use the wizard). I chose Generation 2. I made the mistake of creating a 10gb partition the first time, but this was too small and was running out of space to process large temp files. We’re not storing the actual library files on this machine, so I would recommend 20gb.<\/p>\n\n\n\n

You can use most of the defaults. In Configure Networking, select the switch you just created and in Installation Options, choose your Ubuntu ISO as the install source:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Follow the Ubuntu installation. Ensure that you check the option to install Docker and set eth0 to the external network switch you set up on Hyper-V. I used DHCP and then fixed the IP on the router.<\/p>\n\n\n\n

Mount the NAS<\/h3>\n\n\n\n

Note: I will be using my Ubuntu user ‘david’ and the name of my share \/ mount ‘shared’ for clarity and highlighting<\/mark> any sections you are likely to want to change to match your environment.<\/p>\n\n\n\n

The mount will vary slightly with your SMB version. Googling my router, the result was that it didn’t support SMB2, but in reality, it does. I haven’t tried 2.1, but did try 3.0 with no success.<\/p>\n\n\n\n

As mentioned above, this is for CIFS \/ Samba.<\/p>\n\n\n\n

sudo apt update\nsudo apt upgrade\nsudo apt install cifs-utils\n\n# my NAS folder is shared and will have a folder\n# called paperless\nsudo mkdir -p \/mnt\/shared<\/mark><\/code><\/pre>\n\n\n\n
Next we will create a file with our credentials.<\/p>\n\n\n\n
sudo vim \/home\/david<\/mark>\/.smbcredentials<\/code><\/pre>\n\n\n\n
and save with the user name and password in this format<\/p>\n\n\n\n
username=your_nas_username<\/mark>\npassword=your_nas_password<\/mark><\/code><\/pre>\n\n\n\n
and secure the file:<\/p>\n\n\n\n
sudo chmod 600 \/home\/david<\/mark>\/.smbcredentials<\/code><\/pre>\n\n\n\n
Set up the automatic mounting upon boot:<\/p>\n\n\n\n
sudo vim \/etc\/fstab<\/code><\/pre>\n\n\n\n
and add the mapping:<\/p>\n\n\n\n
# NAS Samba Share\n\/\/192.168.2.1\/shared<\/mark> \/mnt\/shared<\/mark> cifs credentials=\/home\/david\/.smbcredentials,iocharset=utf8,vers=2.0<\/mark>,uid=1000,gid=1000,file_mode=0755,dir_mode=0755 0 0<\/code><\/pre>\n\n\n\n
Install and configure Paperless<\/h3>\n\n\n\n
Start by adding your use to a docker group so you can run the containers:<\/p>\n\n\n\n
sudo groupadd docker
newgrp docker
sudo usermod -aG docker david<\/mark><\/code><\/pre>\n\n\n\n
Use the installation script from https:\/\/docs.paperless-ngx.com\/setup\/<\/a> and install into a directory paperless-ngx<\/code> under your user (don’t run as root). I also recommend using the PostgreSQL database.<\/p>\n\n\n\n
Edit the docker-compose.env file:<\/p>\n\n\n\n
vim \/home\/david<\/mark>\/paperless-ngx\/docker-compose.env<\/code><\/pre>\n\n\n\n
Check the time zone is set correctly. In my case I had to change to:<\/p>\n\n\n\n
PAPERLESS_TIME_ZONE=Europe\/London<\/mark><\/code><\/pre>\n\n\n\n
And add these settings to disable inotify (CIFS does not support this) and instead poll for any documents to ingest from the consume directory. These settings will poll every 20 seconds but also includes a delay as I was having failures without it.<\/p>\n\n\n\n
PAPERLESS_CONSUMER_ENABLE_INOTIFY=false\nPAPERLESS_CONSUMER_POLLING=20\nPAPERLESS_CONSUMER_POLLING_DELAY=3\nPAPERLESS_CONSUMER_POLLING_RETRY_COUNT=3<\/code><\/pre>\n\n\n\n
Next, edit the YAML file in the same directory:<\/p>\n\n\n\n
vim \/home\/david<\/mark>\/paperless-ngx\/docker-compose.yml<\/code><\/pre>\n\n\n\n
Most of this can be left, but under the webserver block (this is the main container which relies on the other dependencies, I have highlighted in bold the changes you want to pay attention to. I changed the port I will access the web server on to 8009, turned off the restart (more on that later) and mapped the internal volumes to the correct folders on my NAS:<\/p>\n\n\n\n
webserver:\n    image: ghcr.io\/paperless-ngx\/paperless-ngx:latest\n    restart: no<\/strong>\n    depends_on:\n      - db\n      - broker\n      - gotenberg\n      - tika\n    ports:\n      - \"8009<\/mark><\/strong>:8000\"\n    volumes:\n      - \/mnt\/shared\/paperless<\/mark>\/data<\/strong>:\/usr\/src\/paperless\/data\n      - \/mnt\/shared\/paperless<\/mark>\/media<\/strong>:\/usr\/src\/paperless\/media\n      - \/mnt\/shared\/paperless<\/mark>\/export<\/strong>:\/usr\/src\/paperless\/export\n      - \/mnt\/shared\/paperless<\/mark>\/consume<\/strong>:\/usr\/src\/paperless\/consume<\/code><\/pre>\n\n\n\n
Configure Paperless as a service to start on reboot<\/h3>\n\n\n\n
I had a lot of issues with rebooting, mainly with finding a configuration which would get the NAS mounted and then correctly start the containers.<\/p>\n\n\n\n
Create a new service file:<\/p>\n\n\n\n
sudo vim \/etc\/systemd\/system\/paperless.service<\/code><\/pre>\n\n\n\n
Add the following which waits for the NAS to finish mounting and includes an addtional sleep of 10 seconds before starting the paperless service:<\/p>\n\n\n\n
[Unit]\nDescription=Paperless-ngx container stack\nRequires=snap.docker.dockerd.service network-online.target mnt-shared<\/mark>.mount\nAfter=snap.docker.dockerd.service network-online.target mnt-shared<\/mark>.mount\n\n[Service]\nType=oneshot\nWorkingDirectory=\/home\/david<\/mark>\/paperless-ngx\nExecStart=\/bin\/bash -c 'sleep 10 && \/snap\/bin\/docker compose up -d'\nExecStop=\/snap\/bin\/docker compose down\nRemainAfterExit=true\nTimeoutStartSec=0\n\n[Install]\nWantedBy=multi-user.target<\/code><\/pre>\n\n\n\n
Enable the service:<\/p>\n\n\n\n
sudo systemctl daemon-reexec\nsudo systemctl daemon-reload\nsudo systemctl enable paperless.service<\/code><\/pre>\n\n\n\n
Backup \/ Export files<\/h3>\n\n\n\n
Ideally, if you had a second NAS available, you could map your export folder there in docker-compose.yml, but keeping things simple, we’ll set up an export to run every night at 02:30 which keeps the last 3 files. You’ll need to do something to copy the exported file elsewhere, or a failure of you NAS will lose your data AND your backup!<\/p>\n\n\n\n
Create a script file:<\/p>\n\n\n\n
vim \/home\/david<\/mark>\/paperless-ngx\/export.sh<\/code><\/pre>\n\n\n\n
Save this in the file:<\/p>\n\n\n\n
#!\/bin\/bash\n\nset -e\n\n# Define paths\nPROJECT_DIR=\"\/home\/david<\/mark>\/paperless-ngx\"\nEXPORT_DIR=\"$PROJECT_DIR\/export\"\nTIMESTAMP=$(date +\"%Y-%m-%d_%H-%M-%S\")\nEXPORT_FILE=\"$EXPORT_DIR\/paperless_export_$TIMESTAMP.zip\"\n\n# Ensure export dir exists\nmkdir -p \"$EXPORT_DIR\"\n\n# Go to Paperless project directory\ncd \"$PROJECT_DIR\" || exit 1\n\n# Run the export\ndocker compose exec -T webserver document_exporter -z - > \"$EXPORT_FILE\"\n\n# Keep only the 3 most recent backups\ncd \"$EXPORT_DIR\"\nls -1t paperless_export_*.zip | tail -n +4 | xargs -r rm --<\/code><\/pre>\n\n\n\n
Make it executable:<\/p>\n\n\n\n
chmod +x \/home\/david<\/mark>\/paperless-ngx\/export.sh<\/code><\/pre>\n\n\n\n
Edit \/ create cron:<\/p>\n\n\n\n
crontab -e<\/code><\/pre>\n\n\n\n
Add this to start at 02:30 and output to a log file:<\/p>\n\n\n\n
30 2 * * * \/home\/david<\/mark>\/paperless-ngx\/export.sh >> \/home\/david<\/mark>\/paperless-ngx\/export.log 2>&1<\/code><\/pre>\n\n\n\n
The Finish Line<\/h2>\n\n\n\n
You should be ready to go!<\/p>\n\n\n\n
cd \/home\/david<\/mark>\/paperless-ngx\ndocker compose up -d<\/code><\/pre>\n\n\n\n
It takes a little while for the webserver to start (check its status with docker ps<\/code>).<\/p>\n\n\n\n
Once the status for the for the main paperless container is up and healthy, navigate to your install (for me http:\/\/192.168.2.1:8009)and follow the instructions to set up your first user and get started with Paperless-NGX.<\/p>\n\n\n\n
Please feel free to ask any questions in the comments, and I hope this helps!<\/p>\n","protected":false},"excerpt":{"rendered":"
What is Paperless NGX? Paperless is a mature document management system with lots of features. NGX is the latest fork. I highly recommend it, but I won’t go into the features here – just search YouTube for some videos and there is lots of information. So, if there is lots of information, why would you […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31],"tags":[28,30,29],"class_list":["post-137","post","type-post","status-publish","format-standard","hentry","category-guides","tag-docker","tag-hyper-v","tag-paperless-ngx"],"_links":{"self":[{"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=\/wp\/v2\/posts\/137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=137"}],"version-history":[{"count":12,"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=\/wp\/v2\/posts\/137\/revisions"}],"predecessor-version":[{"id":153,"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=\/wp\/v2\/posts\/137\/revisions\/153"}],"wp:attachment":[{"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/david.lidstone.me\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}