Oh cool connection is secure for me now
yeah xD it was giving me errors since evening
since last 8 attempts
Soo can we try it now? To see what CORS error we get now? 😅
yeah sure
oooh dry runs. Wait but why does it work with dry runs? 😳
You need to change a few variables in .env:
- _APP_ENV set to
production - _APP_DOMAIN set to
appwrite.idta.in - _APP_DOMAIN_TARGET set to
appwrite.idta.inThendocker compose downanddocker compose up -dto restart
Then domain should be known, and dry runs should no longer occur.
but the ssl is configured right? I should this still?
No idea how SSL got configured in development mode with dry runs. It should not be working. So I would prefer doing it
This is already set
okay cool
yeah, well, then we sohuld be set. Any CORS errors now?
nope now its giving 400
screenshot? 👀
ok its working now, it the password was less than 8 chars
🎉
Thanks this is working now.
Cool so it was HTTPS in the end. Integersting. Good to learn.
So conclusion, Please install SSL guys :)
Thanks :)
[SOLVED] Cors error on the custom domain
Recommended threads
- Any way to temporarily bypass the email ...
Hey guys, any way to bypass the email verification to use the accounts again? i need to recover some projects that due to recent changes have been stopped, and ...
- Collections list not showing up when try...
I'm trying to create new relationship attribute but both one way and two way relationship is not showing up collections list to connect with my relationship att...
- I have try to use the appwrite in to the...
Invalid Origin. Register your new client (oailedjdbkhlkakmnnapoonllbnfmfij) as a new Web (Chrome Extension) platform on your project console dashboard