Recovering Paperless Instance

[SethGower]

Hello,
I have been having some trouble with getting my paperless instance recovered, after an issue on my NAS caused the apps to fail. I am using TrueNAS Scale, and was running paperless-ngx in the "Apps" system (which uses kubernetes in the background). I was using the TrueCharts version of the app (I believe the last version I was running was 7.0.32 for the chart version, according to the charts directory in the apps config stuff). Long story short, I can't get the apps running, due to some issue with k3s that I don't know how to fix, so I am jumping ship and just moving all of my services to running on normal docker (through portainer). I have access to (I believe) all of the necessary data to run paperless, but I am having trouble getting it all running again. It seems there might be files missing from the postgresql data config, and also some username changes that are causing issues. I copied over the pg_hba.conf, postgresql.conf, and postgresql.auto.conf from a version of TrueNAS's chart that I spun up in a VM (since the former two were missing in the postgre data directory for the original instance). But now it seems I am having an issue with the username/password and such for the database, the truecharts version used the username/password paperless-ng and it seems the docker image I am trying to run is trying to use paperless.

These are the various config volumes I was able to get access to on the TrueNAS box

I believe they are, in order

• Redis
• PostgreSQL
• Paperless Data
  I had the actual media stored elsewhere, not in a PVC. And I have verified I have all of the PDFs (originals, and archives) and I have the thumbnails directory.

If anyone can offer any advice/suggestions on how to recover this instance, so I can migrate properly, that would be amazing.

I could obviously just start from scratch, but I would prefer to try to recover the metadata that the instance had, since I have a lot of documents. Unless that's all stored in the PDFs as well, and I could just have a new instance consume it and it would just magically work. If that's the case, let me know.

[stumpylog]

• the Redis data is basically irrelevant, there's nothing really stored there except in flight tasks, which don't stay long
• You can set the user/password for the database, see https://docs.paperless-ngx.com/configuration/#database
• The media directory needs to either be in the volume or in a bind mount and set via configuration
• Definitely look into the exporter for next time, it's must easier

[SethGower]

Thank you so much, this was a ton of help. I didn't realize you could just use all of those options as an environment variable. Once I got there, I had to figure out what the password was for the database (it wasn't paperless-ng like I thought, it was a random string that was stored as a kubernetes secret). I have now gotten the portainer instance up and running and I have my documents and everything working. So thank you for your help.

[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.