
i am using Cloudflare to add custom domain in appwrite console i got 3 issue.
- Domain Verification failed message
- after domain verification failed when i hot the custom domain url its working actully but it redirect to the AppWrite console after login i can see all my projects.
- after deploye flutter web added custom domain and all the configuration but got error like this when i logged in in my flutter web project "Access to XMLHttpRequest at 'https://quoteheaven.life/v1/account/sessions/email' from origin 'https://quote-heaven.pages.dev' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://localhost' that is not equal to the supplied origin."

Domain verification failed Domain hosted on CloudFlare

Domain Verification failed message
Yes, this is expected because the IP address doesn't match appwrite cloud. It's fine, though because Cloudflare will be generating your certificate and not Appwrite.
it redirect to the AppWrite console after login i can see all my projects.
This is expected and fine.
CORS policy: The 'Access-Control-Allow-Origin' header has a value
Double check you've added a web platform that matches the hostname of your app. Also double check your project ID is set and correct.
One of the biggest reasons why you use a custom domain is so that your app and appwrite will have the same base domain and the appwrite session cookie will be considered a 1st party cookie. so, make sure your prod app will be on the same base domain

For the domain verification issue you can disable proxy, do verification and enable proxy in cloudflare DNS tab
Recommended threads
- API Endpoint to Verify Password.
I have 2 use cases where i need to verify a users password outside of login, e.g. Updating user account data (such as name, or prefs, or data in a users databa...
- search collection by document ID
How to filter or search collection for a document using document ID, I can't find this item on the filter menu
- Database Migration/Sync Between Two Proj...
Overall The migration failed mainly due to conflicts with existing data (documents, attributes, collections, etc.), exceeding attribute limits, and unsupported ...
