Oh cool connection is secure for me now
[SOLVED] Cors error on the custom domain
Votes
1
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
yeah xD
it was giving me errors since evening
Rank 3: Container
since last 8 attempts
Soo can we try it now? To see what CORS error we get now? 😅
Rank 3: Container
Rank 3: Container
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.in
Thendocker compose downanddocker compose up -dto restart
Then domain should be known, and dry runs should no longer occur.
Rank 3: Container
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
Rank 3: Container
This is already set
okay cool
yeah, well, then we sohuld be set. Any CORS errors now?
Rank 3: Container
Rank 3: Container
nope now its giving 400
screenshot? 👀
Rank 3: Container
ok its working now, it the password was less than 8 chars
🎉
Rank 3: Container
Thanks this is working now.
Rank 3: Container
Cool so it was HTTPS in the end. Integersting. Good to learn.
Rank 3: Container
So conclusion,
Please install SSL guys :)
Rank 3: Container
Thanks :)
[SOLVED] Cors error on the custom domain