I currently have a love hate relationship with it, but that’s mostly because of issues outside of paperless. I had been uploading to my server automatically with Nextcloud, and processing the files with paperless as they came in. Next thing I know, all the files are gone and none of the documents are available in paperless any longer, just the OCR translations that… leave something to be desired sometimes.
I’ve scrapped the whole thing in the short term, and will likely try again in the long term. Just need to find the time.
Sounds like maybe you ran it as a container and didn’t mount the document archive externally then updated the container. That would have likely blown away the actual ingested documents but left the Metadata (including the OCR data) where it was, assuming the database was either its own container or mounted externally
I encountered such problem the moment when watchtower pulled the latest update, including postgres:16.
After setting the docker compose file back to postgres:15.4 and updating the stack, all data reappeared.
I currently have a love hate relationship with it, but that’s mostly because of issues outside of paperless. I had been uploading to my server automatically with Nextcloud, and processing the files with paperless as they came in. Next thing I know, all the files are gone and none of the documents are available in paperless any longer, just the OCR translations that… leave something to be desired sometimes.
I’ve scrapped the whole thing in the short term, and will likely try again in the long term. Just need to find the time.
Sounds like maybe you ran it as a container and didn’t mount the document archive externally then updated the container. That would have likely blown away the actual ingested documents but left the Metadata (including the OCR data) where it was, assuming the database was either its own container or mounted externally
Nah, the container had an external volume for storage. That’s one of the first things I checked.
Where did the docs go?
I believe the server purged them for space? Not really sure tbh.
I encountered such problem the moment when watchtower pulled the latest update, including postgres:16. After setting the docker compose file back to postgres:15.4 and updating the stack, all data reappeared.
This could have been it. At this point the data is fully lost though, as I killed the container completely.