Skip to content
Back

I have troubles with login to appwrite console after updating to 1.7.4 from 1.6.1

  • 0
  • Self Hosted
D5
26 May, 2025, 16:18

Oh

TL;DR
Developers are experiencing login issues with the Appwrite console after updating from version 1.6.1 to 1.7.4. To resolve the problem, they should create backups before modifying anything, follow migration instructions explicitly, and ensure that the `_console_rules` table rows in the database are fixed. If backups are not available, restoring to version 1.6.2 before upgrading to 1.7.4 is recommended. Be cautious with docker-compose file changes and seek the core team's help if needed.
Nevets
26 May, 2025, 16:18

appwrite container logs

D5
26 May, 2025, 16:18

Then you're screwded I think

D5
26 May, 2025, 16:19

Copy and paste here the logs, it's difficult to read them

Nevets
26 May, 2025, 16:19

[Error] URL: /v1/account/sessions/email [Error] Type: Appwrite\Extend\Exception [Error] Message: Unknown resource type [Error] File: /usr/src/code/app/controllers/general.php [Error] Line: 761 [Error] Timestamp: 2025-05-26T16:12:02+00:00 [Error] Method: GET [Error] URL: /v1/account [Error] Type: Appwrite\Extend\Exception [Error] Message: Unknown resource type [Error] File: /usr/src/code/app/controllers/general.php [Error] Line: 761 [Error] Timestamp: 2025-05-26T16:12:03+00:00 [Error] Method: POST [Error] URL: /v1/account/sessions/email [Error] Type: Appwrite\Extend\Exception [Error] Message: Unknown resource type [Error] File: /usr/src/code/app/controllers/general.php [Error] Line: 761 [Error] Timestamp: 2025-05-26T16:15:00+00:00 [Error] Method: GET [Error] URL: /v1/databases/:databaseId/collections/:collectionId/documents [Error] Type: Appwrite\Extend\Exception [Error] Message: Unknown resource type [Error] File: /usr/src/code/app/controllers/general.php [Error] Line: 761

D5
26 May, 2025, 16:20

Did you have some version prior to 1.6.2 installed?

Nevets
26 May, 2025, 16:21

the server is fairly new, I don't think so. I'm not sure what exactly 1.6.2 was there, but 1.6.n is for sure.

D5
26 May, 2025, 16:22

And you ran migrations after upgrading to 1.6.2?

Nevets
26 May, 2025, 16:24

I had 1.6.2 for a couple of months, then installed 1.7.2 and migrated the project to it as in the manual

Nevets
26 May, 2025, 16:25

or maybe i had 1.6.1 for couple of month

Nevets
26 May, 2025, 16:25

I don't remember exactly.

D5
26 May, 2025, 16:25

The manual shows you should perform backups. That was not clear? 😅

D5
26 May, 2025, 16:26

Well, I'm asking in order to edit it and set it to something better as I'm seeing many people upgrading and not performing backups 😬 (you're not alone unfortunately)

D5
26 May, 2025, 16:27

Well, that could be the issue

Nevets
26 May, 2025, 16:27

I've had too many positive experiences with major updates before, I've been using appwrite for a couple of years. I was relaxed...

Nevets
26 May, 2025, 16:28

Which cannot be solved?...

D5
26 May, 2025, 16:36

It can, but probably it's not easy

Nevets
26 May, 2025, 16:42

Can you tell me where to look please? It would be a pity to lose everything

Nevets
26 May, 2025, 16:44

docker-compose down docker-compose rm -f docker rmi appwrite/appwrite:1.7 docker-compose up -d

Can I try it?

D5
26 May, 2025, 16:47

NO

D5
26 May, 2025, 16:47

That will delete everything permanently!

D5
26 May, 2025, 16:48

You need to enter into the DB and modify things but I have no idea cc @Steven

D5
26 May, 2025, 16:51

Well, sorry, the DB isn't deleted but the issue is not with the containers but with the DB and deleting it will delete everything

D5
26 May, 2025, 16:52

@Nevets Can you check what are the logs for the database? the container name is appwrite-mariadb

Nevets
26 May, 2025, 16:52

ok

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