
i have recently tryed to update my self hosted instance from 1.4.13 to 1.5.0, but getting this error as shown in the image. Why is it happening? Can somebody help me please. I run the upgrade comand as documented here https://appwrite.io/docs/advanced/self-hosting

Please use 1.5.1

is it not that i have to first upgrade to 1.5.0 and run the migrations and then 1.5.1?

ok i successfully installed the 1.5.1 but somehow now i cannot run the migration it says this

right now i have rolled it back to 1.4.13

you mean you're using the default password 🧐

yes the values in my .env file are the standasd for database

previewsly i were able to upgrade normally but since 1.5 not

i see in my synology docker container that the database and some other worker containers are stopping. maybe thatswhy, but this is just happening when i upgrade to 1.5.x and its not happen with 1.4.x

what was in your mariadb logs?

logs for appwrite looks like this


and for mariadb like this


and the container looks not running


when i try to start it manually it stops then again

why is it like this. I have upgraded to 1.5.3 and still the mariadb container is not running and get the same error with migration script.

is it something from my side or what?

something is wrong with your mariadb. you should probably restore from backup

yes i ran the restore script successfully right now and also before but when i try to run the migration script it fails. And because of that i am not able to access my appwrite at all.

getting error while updating to 1.5.X

When you restore, are the backups from 1.4.13?

yes

what's the output of docker ps -a
? you would want to start the process on 1.4.13 images
Recommended threads
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
