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?
Summary
Developers are experiencing issues connecting GitHub to their third project on Appwrite, getting a "document_already_exist" error. They suggest checking the .env file and DNS records, running `docker compose logs appwrite`, and migrating to a new instance as a workaround. The developers also discuss past migrations, upgrades, and successful integrations on other projects. No specific solution is provided in the thread.
D5
Moderator
Nov 10, 2024, 15:49
Was it an old instance that you upgraded or similar?
Timo
Rank 1: Thread
Nov 10, 2024, 17:14
yup it is.
Timo
Rank 1: Thread
Nov 10, 2024, 17:14
The original projects - those where the integration works - where setup before I upgraded the instance
D5
Moderator
Nov 10, 2024, 20:01
Do you have run migration command after upgrades?
Timo
Rank 1: Thread
Nov 11, 2024, 17:19
Sure. I migrated a while ago, and haven’t had any issues with something else since.
Timo
Rank 1: Thread
Nov 12, 2024, 18:00
Do you have any other idea how to fix this?
Move everything over to another instance, and wipe this one?
D5
Nov 12, 2024, 18:02
What are the docker compose logs for the appwrite main container?
D5
Nov 12, 2024, 18:02
You can get them by running docker compose logs appwrite
Timo
Rank 1: Thread
Nov 13, 2024, 20:40
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.