Errors in Community Version after changing AES encryption key

Product Feedback
1

Since the Cloud version is not working yet because of the 429 errors, I tried to setup a local version.
It works with the example docker-compose.yml file, but if you change the AES Encryption and JWT keys it starts giving 500 errors.
Anyone have any idea?
thanks

2

I believe for security reasons, the AES key/JWT key cannot be modified after Docker has started. A possible approach i think is to modify these keys in the Docker Compose file, then delete the Docker volume, and restart Docker. It allows all data to be initialized.

1 Like
3

The error was resolved.
I think it was related to spaces between the AES keys and comments after the keys in the .yml file