-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: Migration Error while migrating to 1.4.1 #6139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @spasma , can you try upgrading from 1.3.8->1.4.0 and then 1.4.1 once? |
Sadly that doesn't do the trick either, just saw that downgrading is also not possible. All tabs in my projects give 500 errors now, except the overview tab. |
@spasma With a similar issue as yours i managed to downgrade from v1.4.1 back to v1.3.8 by running the installation command for v1.3.8 (as in the docs) and then restarting appwrite with |
Awesome! Shall I close this then @spasma |
@joeyouss Yes, that's okay. Issue isn't fixed, but I'll stay on 1.3.8 for now.. |
For me this isn't fixed either, migration fails with a similar message on Ubuntu 22.04, and I don't know how to upgrade to the current version. |
FYI for appwrite devs: I'm running on ubuntu 22.04 as well |
Since my installation was (until now) only for testing purposes I decided to uninstall Appwrite with |
Oh well, recreated everything as well. Lost all production data, downgrading seem not to work. Still 500 pages everywhere. |
Maybe you're able to set up a new instance of v1.4.2 and import your data (in project: Settings - Migrations) from the corrupt one? |
Uh oh!
There was an error while loading. Please reload this page.
👟 Reproduction steps
I tried to migrade from 1.3.1 to 1.4.1.
👍 Expected behavior
I expected it to migrate succesful to 1.4.1
👎 Actual Behavior
It failed. After it failed I tried again by migrating to 1.3.8 first (which was successful). But while migrating from 1.3.8 to 1.4.1, it showed the same error message.
This is the output of the Migration script:
🎲 Appwrite version
Version 1.3.x
💻 Operating system
Linux
🧱 Your Environment
I'm using docker on a Ubuntu system.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: