Back

[Solved] Upgrade from appwrite 1.2.1 to 1.3.0 issues

  • 0
  • General
jadechessink
11 Oct, 2023, 23:30

Parent folder is /docker, appwrite is inside the /docker folder, inside of /docker/appwrite is my docker-compose.yml.

ran the following to update appwrite:

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

Tried manually specifying the folder:

TypeScript
docker run -it --rm     --volume /var/run/docker.sock:/var/run/docker.sock     --volume /docker/appwrite:/usr/src/code/appwrite:rw     --entrypoint="upgrade"     appwrite/appwrite:1.3.0

both resulted in the following errors:

TypeScript
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "upgrade": executable file not found in $PATH: unknown.

i can confirm this was run from the parent "/docker" folder as specified in the directions.

i also tried to run it with other versions of appwrite 1.3.x and it also failed. Docker-compose.yml has been minimally changed to facilitate some volume binding. docker-compose attached.

Just wanted to know if this is due to me changing the volumes in the docker compose, or if theres some other issue at play here, and if there is, what it might be.

TL;DR
Summary: The user encountered issues while upgrading from Appwrite 1.2.1 to 1.3.0. They found that the issue was a misconfiguration of the openssl key in the .env file. The user also had trouble logging in after the upgrade and suspected a problem with their docker volume binds. To troubleshoot, they were advised to check the console users table in the database and try reloading Docker. The user also asked if there was a way to reset their password from the CLI. Solution: 1. Compare the current .env file with the previous one to ensure the openssl key is correct. 2. Connect
Binyamin
11 Oct, 2023, 23:34

Change from upgrade to install

Binyamin
11 Oct, 2023, 23:34

The entry point upgrade is only from version 1.4

jadechessink
11 Oct, 2023, 23:34

Understood, ill give that a go! thank you.

jadechessink
12 Oct, 2023, 00:32

that was able to work just fine, but i did run into an interesting issue when testing the upgrade, i was no longer able to log into appwrite, but as far as i can tell it still sees my users.

is there a way to reset my password from CLI?

Binyamin
12 Oct, 2023, 00:33

Nope. Only by connecting to the database or use SMTP to reset the password Did you try to reload your docker?

jadechessink
12 Oct, 2023, 00:34

i did, but ill give it another try, heres the error seen inthe logs: appwrite | [Error] Timestamp: 2023-10-12T00:33:28+00:00 appwrite | [Error] Method: POST appwrite | [Error] URL: /v1/account/sessions/email appwrite | [Error] Type: Appwrite\Extend\Exception appwrite | [Error] Message: Invalid credentials. Please check the email and password. appwrite | [Error] File: /usr/src/code/app/controllers/api/account.php appwrite | [Error] Line: 184

Binyamin
12 Oct, 2023, 00:35

Connect to your database and check the console users table

Binyamin
12 Oct, 2023, 00:37

Use this gist to connect directly to your database and check if the data is being update in realtime

jadechessink
12 Oct, 2023, 01:22

it looks to have over written my volumes, which is fine as this was test before the actual upgrade.

im thinking this has to do with my docker volume binds, i have a docker-compose.override.yml set so i wouldnt expect it to have done that to my data, did i make a mistake somewhere?

jadechessink
12 Oct, 2023, 01:57

i was wrong, i was looking at the wrong table, the _console_users do show correctly in the DB, but im still unable to log in, so the data is there, but its not logging in for some reason

jadechessink
12 Oct, 2023, 01:58

the passwords also show for the users as well

Drake
12 Oct, 2023, 02:46

Compare your current .env to your previous one. Is the openssl key correct?

jadechessink
12 Oct, 2023, 03:05

as always Steven, your the best, that was absolutely it, it got changed, i set it correctly and it resolved the issue.

jadechessink
12 Oct, 2023, 17:28

[Solved] Upgrade from appwrite 1.2.1 to 1.3.0 issues

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more