Mastodon Update 4.3.1
Problem after Update the Mastodon Server from 4.2.13 to 4.3.1
Mastodon not start anymore and the log file show: to generate new secrets and then assign the environment variables.
I found already the command to generate the scret keys: sudo docker exec -it -w /app/www mastodon bin/rails db:encryption:init
But i don´t know how i can set the secrets key to ".env.production"
Does anyone have instructions or could help me?
Run
bin/rails db:encryption:init to generate new secrets and then assign the environment variables.
mastodon | Do not change the secrets once they are set, as doing so may cause data loss and other issues that will be difficult or impossible to recover from.
mastodon | Exiting
mastodon |
mastodon | Mastodon now requires that these variables are set:
mastodon |
mastodon | - ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY
mastodon | - ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT
mastodon | - ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY
mastodon |
mastodon | Run bin/rails db:encryption:init to generate new secrets and then assign the environment variables.
mastodon | Do not change the secrets once they are set, as doing so may cause data loss and other issues that will be difficult or impossible to recover from.
mastodon | Starting sidekiq handling all queues with 5 threads 5 Replies
@JigSaw can you please help here
Seems a config field is missing for this app
https://github.com/mastodon/mastodon/releases/tag/v4.3.0
This release contains upgrade notes that deviate from the norm:
‼️ Requires new encryption secrets environment variables
GitHub
Release v4.3.0 · mastodon/mastodon
Upgrade overview
This release contains upgrade notes that deviate from the norm:
‼️ Requires new encryption secrets environment variables
⚠️ The minimal supported version for PostgreSQL has been bu...
Our automated update system didn’t detect the breaking change due to the version not being breaking
Did you find a solution?
I pushed and update which includes the required environment variables
The solution was I restored the backup and did not do the update.
I will try the new update Thanks