Manual update of redis and postgres leading to error of paperless-ngx

[Pandafibre]

Hi,
I'm a bit at a loss here. I'm not a coder and don't know much about it, but I have managed to install paperless ngx through docker on a synology and it worked flawlessly. I'm using watchtower also to keep my containers updated.
Today in the morning I saw an available update for redis and postgres and in my stupidity, I clicked on update.
Now paperless and even Joplin don't work anymore, and what I see in the logs is this (see html file attached).
Any way you guys can help me?

Would be much appreciated since it's one of my most important containers.

[shamoon]

Have you tried re-creating the paperless-ngx container? I dont know Synology but e.g. this: https://www.wundertech.net/how-to-update-docker-containers-on-a-synology-nas/#Updating_Docker_Containers_on_a_Synology_NAS_Using_the_Docker_Application

[shamoon]

If you have properly mapped those volumes then you should be fine, thats one of the big ideas of docker, you can preserve data but easily "re-install" (i.e. a fresh container) the software.

Of course, take a backup first and then you have an insurance plan =)

[Pandafibre]

How do I make a backup xD. Sorry but I'm just not a programmer.

[Pandafibre]

You mean saving all the folders of paperless ngx manually?

[shamoon]

There are a few different backup strategies but: https://docs.paperless-ngx.com/administration/#backup

In general, if you are self-hosting anything you should have a backup plan in-place in case of e.g. hardware failure, data loss, etc, super important! The web is chock full of helpful tutorials, I'd encourage you to dive in

Everyone starts somewhere and you certainly dont need to be a programmer =)

[Pandafibre]

Ok thanks! I copied all the folders to another place for backup, reployed the stack with portainer. There was one error message but now it works again!!!! Thank you so much!

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