Skittlesthehusky

Hi, I'm having a weird situation where after I updated my Redis, Postgres, and Ghostfolio docker containers, the security token that was used for my instance's admin account is now no longer working, almost as if the container is behaving like it's brand new? This has been an issue in the past where I've experienced the same situation, and I was forced to reinstall the Ghostfolio docker image after the update was ran. It's never clear as to why this happens either, so I was hoping I could receive some pointers from someone who's more experienced with this Ghostfolio instance than I am. When I check the logs, I don't see anything noteworthy. Ghostfolio loads the databases just fine and there has been no changes to the actual data to the database as far as I'm aware. I'm unsure if this is an issue that's persistent with Ghostfolio itself or if it's the docker container that tends to misbehave. All variables set in all containers are unchanged. 🤨 Has anyone else experienced this issue and has there been a solution to this problem yet? EDIT: This ended up happening a second time and I took a rough guess that perhaps it was a persistence or stability issue on my end. I was able to restore functionality by both dumping and restoring the Postgres database, as well as building a separate Redis instance on virtual machines I built using Proxmox instead of dockerized images. Why this fixed my issue is beyond me! But unfortunately due to a couple other experiences I've had with this app, I decided it's best for me to find another solution as Ghostfolio seems to have other issues and limitations that have also been outlined by others in their Github. As a tiny side-quest since I had access to the tables, I also tried to see if there was a way to restore the user account via access token, the user-set access token salt value, and the associated user-generated security token as a potential hack-job recovery option for situations like these, but unfortunately it doesn't look like it's possible with my current knowledge and I don't have any extra time to dedicate to finding that out. With no additional documentation and only the source code to work with, further troubleshooting of weird issues like this moving forward is difficult. However, that's a Ghostfolio issue and not a Unraid issue. Thanks for your work to bring this app to Unraid. Hopefully others don't run into the same issue I did! Much love.