Sorry, I can't read through this because it has all the logs rather than the logs for the executor container
Oh sorry for that...here is the proper logs file
Hmm...that's serious. Need to resolve that
maybe you had an old installation of appwrite or something happened with the new installation. are you okay with wiping the data?
Yes
Do you recommend that?
if you're okay with it, yes. to wipe the data, run:
docker compose down -v
Then, start the stack up again with:
docker compose up -d
Thanks. Now works. But I am faced with this problem I have been battling from before. The endpoint has been a real issue, and I could not find any help on the docs either
Would really appreciate your input
Here is the log from the docker compose logs appwrite:
sorry, this is tiny and i can't really see what's going on
what's the output of docker ps -a?
i would like to make a request that we have a video call and i share my screen while you direct me on how to resolve this issue
i would be elated if you respond
because i am having an issue with connecting with the db, unable to sign-up, what are the plaussible soln
the error below
what can i do to do away with this
no, docker ps -a please
So it should be running on port 443...what happens when you browse to https://localhost/
It works absolutely fine
ok so your appwrite is running fine
So this is your problem now, right? what did you use as your endpoint when you called client.setEndpoint()?
Recommended threads
- Auth not working on expo react native
I'm trying to launch a development server with expo go and appwrite as a backend. On my windows pc, I've got a local docker instance of appwrite running as my b...
- Urgent help required - Could not resolve...
I upgraded my production environment to 1.8.0 but experienced issues with appwrite running out of worker threads. I downgraded back to 1.6.1 and restored the da...
- How to change "collection Id" to "collec...