You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to be lazy and copy the /docker/heimdall directory folders and files to the new NAS and I rebuilt it using compose in Docker Manager but I am getting the Server 500 error whenever I try to add new apps. (I can edit existing ones).
I think the best thing to do is to start from scratch with a new install, but is there a way to save my current database of apps? I looked in the docker/heimdall folders but nothing there seems obvious as to what the database should be.
So, what would I save to restore my applist on a brand new Heimdall docker container?
Thanks in advance.
PS: I am not sure if the Server 500 errors are to do with a version mismatch. I installed it on the old server in September and had WATCHTOWER running, so I do not know if it updated or not. (I stopped using WATCHTOWER on the new server, and will just pull newer images manually).
The text was updated successfully, but these errors were encountered:
I tried to be lazy and copy the /docker/heimdall directory folders and files to the new NAS and I rebuilt it using compose in Docker Manager but I am getting the Server 500 error whenever I try to add new apps. (I can edit existing ones).
I think the best thing to do is to start from scratch with a new install, but is there a way to save my current database of apps? I looked in the docker/heimdall folders but nothing there seems obvious as to what the database should be.
So, what would I save to restore my applist on a brand new Heimdall docker container?
Thanks in advance.
PS: I am not sure if the Server 500 errors are to do with a version mismatch. I installed it on the old server in September and had WATCHTOWER running, so I do not know if it updated or not. (I stopped using WATCHTOWER on the new server, and will just pull newer images manually).
The text was updated successfully, but these errors were encountered: