The upgrade seemingly completed without a hitch, I almost gave the credit on how seamless it was, until appwrite refused to come back up and is now completely broken.
It seems there's logs related to
TypeScript
Stack trace:
#0 /usr/src/code/app/http.php(303): createDatabase(Object(Utopia\Http\Http), 'getLogsDB', 'logs', Array, Object(Utopia\Pools\Group))
#1 [internal function]: {closure:{closure:/usr/src/code/app/http.php:291}:294}()```
I use remote MariaDB rather than the built in, and it seems everything else can connect fine, I see the connections from the other containers, but for some reason it's trying to access the "appwrite" database, when that's not what the database is even called in the env, there is no appwrite db, we've renamed it, and it's set in the env, using it fine in 1.8.1
TIA!
TL;DR
Issue: After upgrading to 1.9, developers are experiencing a fatal error related to creating a logs table in the appwrite database from a remote MariaDB. The error indicates an access denied issue for the 'backend' user to the 'appwrite' database, even though the database is renamed in the environment variables and was functioning properly in version 1.8.1.
Solution: Check the database connection settings in the environment variables and ensure that the correct database name is being referenced in the appwrite configuration. Additionally, verify the permissions for the 'backend' user on the database to resolve the access issue.Recommended threads
- It says domain already used but I have d...
I accidentally deleted the project in which I used my domain originally (orexia.app) from name.com. Now I am trying to add it to a different project and it says...
- Is this normal in the self host custom d...
when i try to add custom domain to the project did not see this in 1.8.0 ok when pressed the retry it says "DNS verification failed with resolver 8.8.8.8. Domai...
- No server error on selfhosted appwrite
Please help me, my clients is ask what happen on their data? How can i make it up again?