Skip to content
Discussion options

You must be logged in to vote

I landed here after I had the same error.

In my scenario, I had previously spun up docker compose to test litellm with different salt and master key then did docker compose down assuming it will destroy everything.

Next I spun up again with different config and got the above error. I found that docker compose uses volumes that doesn't get destroyed and there were some DB entries encrypted with past master key and salt. Had to delete it using docker compose down --volumes --remove-orphans and then docker compose up. This fixed my issue.

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by krrishdholakia
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants