Recent restored documents, not getting 404 Not Found for every document

[bukyo]

After using document_exported to create a backup, I recently reinstated a paperless-ngx install on docker on my NAS.

I've used the document_importer to restore all settings, and on the main documents page, I can see the thumbnails and document information (Tags, correspondents, titles etc). I can even download the file or view it using the eye icon.

However, if I use the edit button for any document, the page starts to load (http://paperless.nas/documents/364). I see the empty text boxes and page layout, but before populating this with the document data, it kicks out to a 404 Not Found page (http://paperless.nas/404) with Paperless-ngx branding, and a button labelled Go To Dashboard.

I've managed to edit the permissions of the documents to either none, or the user I am logged in with, however I can't seem to get to the edit page for any document.

I can't see anything in the logs to help identify the cause. Anyone know what causes this problem?

[stumpylog]

Double check your documents are actually present in the file system, at the correct locations as configured and volumes as mapped

[bukyo]

Thank you. This was it.

Although they were all originally stored in the media/documents/originals main folder, it looks like at some point the storage path in paperless had been updated to {created_year}/{correspondent}/{document_type} so it didn't match the actual locations.

The weird thing was it would still download the file when I chose the download link (not sure how if the original was in the 'wrong' location), just not open/edit the paperless record.

Ultimately, I left it for a couple of weeks and it looks like it's fixed the structure (I guess it's automatically moved the files) and now all documents are under the 'correct' media/documents/originals/{created_year}/{correspondent}/{document_type} subfolders. I'm getting quite a few files in there now, so it's probably a good time to be separating them out into individual years.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. Please see our contributing guidelines for more details.

[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. See our contributing guidelines for more details.