Hello everyone,
I am trying to connect GitHub to a third project, but everytime i get redirected back to Appwrite it fails with document_already_exist
For now i have spun up another instance to circumvent this. Is there reason why the connection would work on the first two projects, but fails on the third?
Was it an old instance that you upgraded or similar?
yup it is.
The original projects - those where the integration works - where setup before I upgraded the instance
Do you have run migration command after upgrades?
Sure. I migrated a while ago, and haven’t had any issues with something else since.
Do you have any other idea how to fix this? Move everything over to another instance, and wipe this one?
What are the docker compose logs for the appwrite main container?
You can get them by running docker compose logs appwrite
That is quite interesting. I was getting the same error yesterday when i tried to use the migration tool to move some projects of that instance.
I checked, and the .env contains all the right domains, and the dns records are set correctly.
Recommended threads
- Error upgrading from 1.8.1 to 1.9.0
DO Self-hosted server failed to upgrade with this error "Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.42". U...
- MariaDB refuses to connect to appwrite
Earlier, I tried updating my Appwrite version from 18.1.x to the latest release because my Flutter package required it to function properly. I used the official...
- executeFunction intermittently throws Fo...
Environment: Flutter app using the Appwrite Flutter SDK, calling executeFunction for [describe endpoint, e.g. live-stream-related function]. *Description*: Int...