I haven’t updated for a while and was still running 1.7.14, (self hosted) wanted to update to 1.9.7 today,
but receive 503 /Appsmith server is unavailable when restarting appsmith.
I updated first the 1.9.2 checkpoint version and then to 1.9.7
From the log file I can see that Mongock started the data migration
then
[2023-02-13 09:36:41,652] - FAILED OVER - {“id”=“make-applications-public”, “type”=“execution”, “author”=“”, “class”=“DatabaseChangelog2”, “method”=“makeApplicationsPublic”}
[2023-02-13 09:36:41,660] - Mongock migration aborted and DB transaction not enabled. Starting manual rollback process
[2023-02-13 09:36:41,661] - ChangeSet[make-applications-public] does not provide rollback method
[2023-02-13 09:36:41,666] - Mongock has finished
[2023-02-13 09:36:41,666] - Error in mongock process. ABORTED MIGRATION
[2023-02-13 09:36:45,909] - Application run failed
[2023-02-13 09:36:41,666] - Error in mongock process. ABORTED MIGRATION
io.mongock.api.exception.MongockException: Error in method[DatabaseChangelog2.makeApplicationsPublic] : Unable to invoke Cipher due to bad padding
This usually means that in your docker.env, APPSMITH_ENCRYPTION_SALT or APPSMITH_ENCRYPTION_PASSWORD property value has extra space in front or at the end. Can you please verify if thats the case?
Hello @passana! Sorry for the delay. Could you please update first to v1.9.2, which is the checkpoint version, and then to the latest version. Please follow the steps from this guide. Let us know if this works for you.
Could you please share logs from when you migrated to 1.9.2? The one you shared is from 1.9.7 and it only shows the cipher failure. We would like to make sure of whether there were any failures during the 1.9.2 migration.
Hello Eduard!
Are you using the built-in internal MongoDB or an external/custom MongoDB?
Can you please also confirm if you have copied the encryption password and salt to the new environment after you have backed up the data? If you did not, you need to take these values from the stacks/configuration/docker.env of the old instance and copy them to the new instance in the same file, as per this documentation about backup.
Thank @Amelia, but I did not backup/recover. I migrated only.
I was able to fix the issue:
I slowly migrated, first to 1.8.1, then to 1.8.10 , then to 1.8.15, then to 1.9,1, then to 1.9.2 … and tested each version if it works.
As 1.9.2 worked fine, I updated to current version (1.9.12) and it still works fine.
I think the missing step was migrating to 1.9.1 as this seems to be an important update.
(1.9.0 was not available
ERROR: manifest for appsmith/appsmith-ce:v1.9.0 not found: manifest unknown: manifest unknown)
in the release list you state “checkpoint update” for 1.9.0, not 1.9.2, please check here:
Hey @passana ! Is it possible for you to share the logs from when you upgraded to v1.9.1 as well as v1.9.2? This will help us figure out exactly what is happening with this upgrade and hopefully help out other users that find themselves in your position faster.
Please send all the logs. If you are concerned about confidential data, it’s best to send it to us per email to support@appsmith.com and add the link to this post as reference.
