folks, hope you all are doing well. At my company we are testing a self-host implementation of growthbook. We made some changes in our deploy to comply with my company's guidelines. Since then, we are facing the issue in the image. The weird think is that we haven't changed the encryption key in this process, so we don't quite get it how to solve the issue. Can you helps us here?

Hi Larissa, what exact changes did you make? It's likely that you were using the default encryption key of

dev

before, but not it is being set to something else in your environment variables. We do have a migration script to help fix this issue if that's what it is

Hello, Jeremy. We have been tweaking our infrastructure, Helm charts deployments etc. But, in practice, we basically replaced our GrowthBook instances/pods by.. other GrowthBook pods. However, we touched neither the database or the encryption key. They have been the same since day 1.

@future-teacher-7046 sorry to bother you again, but can you give us a hand here?

Hi Larissa