Running into a server error on my self-hosted setup after updating to v1.19.0.

Hey everyone, I'm running into a server error on my self-hosted setup after updating to v1.19.0.

The issue only happens during user creation and deletion. Everything else, like password changes and general database functions, is working perfectly. Any ideas on what might be causing this?

I already tried running migration with no luck

cc: @Aashish Atwal @MagikVoid

Share you docker container logs contaning information about the server errors.

Sure

[0] /usr/src/code/app/controllers/api/users.php : 173 -> createDocument()
[1] /usr/src/code/app/controllers/api/users.php : 262 -> createUser()
[2] /usr/src/code/vendor/utopia-php/framework/src/Http/Http.php : 677 -> {closure:/usr/src/code/app/controllers/api/users.php:259}()
[3] /usr/src/code/vendor/utopia-php/framework/src/Http/Http.php : 976 -> execute()
[4] /usr/src/code/vendor/utopia-php/framework/src/Http/Http.php : 857 -> runInternal()
[5] /usr/src/code/app/http.php : 551 -> run()
[6] [internal function] : -> {closure:/usr/src/code/app/http.php:513}()
http.request · 12.6ms · f23509e4

http.method POST
http.path /v1/users
http.response.code 500
level error

Utopia\Database\Exception\Structure: Invalid document structure: Unknown attribute: "emailCanonical"
at /usr/src/code/vendor/utopia-php/database/src/Database/Database.php:5583
at /usr/src/code/app/controllers/api/users.php:173
at /usr/src/code/app/controllers/api/users.php:262
at /usr/src/code/vendor/utopia-php/framework/src/Http/Http.php:677
... 4 more

────────────────────────────────────────────────────────────

it seems like you might have missed migration. emailCanonical is a new column intorduced in 1.9.x

I ran the migration from the web UI during the update. I also tried forcing it via the terminal with docker exec appwrite migrate and also with --force flag, but I'm still getting the same error.

Now this thread is closed but other users are also facing this issue

https://discord.com/channels/564160730845151244/564160731327758347/1500082413177405490

I have 2 appwrite instances on 2 different servers both are facing this issue after updating

Is there a quick fix to this?

How did you update? What was the previous version?

It was 1.18.0

I used

docker run -it --rm
--publish 20080:20080
--volume /var/run/docker.sock:/var/run/docker.sock
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw
--entrypoint="upgrade"
appwrite/appwrite:latest

Went to the serverip:20080 and updated using web UI

It asked me if I wanna switch to mongo but it was grayed so I stayed on mariadb

And ran migration in the same UI next step

Then I started facing this user problem so I ran the

docker compose exec appwrite migrate

Command in cli aswell

But no luck so I used

docker compose exec appwrite migrate --force

Still no luck so I am here now 😔

I heavily rely on one of the instances so if it's possible to do a quick patch like adding the new column manually please let me know it would be great to be back and running asap

The other instance I can wait for a future patch

seems to be more for 1.8.x update looking at : https://github.com/appwrite/appwrite/blob/1.9.x/src/Appwrite/Migration/Version/V23.php#L153 (as v23 is 1.8.x and v24 is 1.9.x)

@user
regarding manual insert, you should be able to do it with :

You also need to do it for all _XX_users (for each project)

Also if someone could check the SQL query, as i just checked in the code to reconstruct the query but didn't check on actual instance.

I didn't get it😵‍💫

But I'll try, so if I update again will it fix itself?

And the manual process seems tedious should I still attempt(not the best at SQL queries)? And will this fix for future projects?

I tried adding the column but that didn't fix anything I took ai help as I am not the best with sql

No luck unfortunately same error

I also want to let you know if I make a new project and make the user's it works

if you migrate again the 1.9.0 i don't think it will work because the migration that add emailCanonical seams to be for 1.8.x.

if you still want to test a fix with migrations, then you will need to :

• revert to 1.8.x from backups
• run migrations
• verify the emailCanonical is now present
• upgrade to 1.9.0

oh so maybe it's the other way, the emailCanonical might exist in the mariadb table, but might be empty which cause the issue ?
could you check on your mariadb instance to see ?