Hi, I downloaded the docker compose and .env file from the official documentation page.
https://appwrite.io/docs/advanced/self-hosting
When I start up the compose with the given command i get the following errors in the log:
appwrite-maintenance exited with code 0
appwrite-mariadb | 2024-04-08 7:59:33 928 [Warning] Access denied for user 'user'@'172.18.0.16' (using password: YES)
appwrite-mariadb | 2024-04-08 7:59:34 929 [Warning] Access denied for user 'user'@'172.18.0.18' (using password: YES)
appwrite-mariadb | 2024-04-08 7:59:34 930 [Warning] Access denied for user 'user'@'172.18.0.13' (using password: YES)
appwrite-mariadb | 2024-04-08 7:59:34 931 [Warning] Access denied for user 'user'@'172.18.0.14' (using password: YES)
appwrite-mariadb | 2024-04-08 7:59:34 932 [Warning] Access denied for user 'user'@'172.18.0.16' (using password: YES)
appwrite-mariadb | 2024-04-08 7:59:35 933 [Warning] Access denied for user 'user'@'172.18.0.18' (using password: YES)
appwrite-mariadb | 2024-04-08 7:59:35 934 [Warning] Access denied for user 'user'@'172.18.0.13' (using password: YES)
appwrite-scheduler-functions | Failed to create connection: SQLSTATE[HY000] [1045] Access denied for user 'user'@'172.18.0.13' (using password: YES)
I am just trying to host it on my local machine.
Could it be that there is an error in the default compose/.env file?
Is there any reason you can’t use the regular install method?
what do you mean by that? for me docker compose is the regular install method
The regular install method is the “Install with Docker” header - running the command there will prompt you with a few questions, then generate your docker-compose.yml and .env files
i see. I want to use the manual thing, since when going to production i want to use nearly the same compose file.
Have you also fetched the .env file?
The install doesnt work for me either. the maintenence container keeps restarting. logs show filter not found
Did you also install by downloading the docker-compose.yml and .env files?
no i did the regular install. but i think mine may have been a docker issue. I resolved the issue by deleting all containers images and volumes that aren't in use (by my other stuff), deleting all builds, updating docker desktop then tried again and it (kind of) worked. All 22 containers are now running. but now i get a gateway timeout localhost (80 and 443). before i could get the home page but no functionality.
I did originally. this may have caused my initial woes... as i was getting the npm ci error
OK I managed to solve it finally by deleting everything described above and doing a fresh regular install then going to the appwrite folder where the generated .env and .yaml are and running docker compose up -d --remove-orphans --renew-anon-volumes --force-recreate. hope that helps
windows btw... obviously. smh. 🤦♂️
Yes I downloaded the newest env file. I did everything according to the documentation page.
Do you have any important information on that production? Maybe you had previous information on that server?
Recommended threads
- Realtime not processing messages
When subscribing to realtime events of database, the client's websocket receives the messages in the websocket feed, but doesn't call the specific message handl...
- problem with some tables (cant read rows...
I have a weird problem with some tables - they wont show the rows (in console it is stuck loading). I checked in mariadb directly and the collection can be read...
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...