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
- Endless certificate generation cycle
Hello, when I try to add the subdomain stats.hedgehog-rp.ru, I get an infinite loop while the certificate is being generated. There are no problems with adding ...
- Realtime not working for some tables
Hi, I've got an issue where I can setup a realtime connection to listen to some tables, but some not all. I have two tables `history` and `users`. Both can be ...
- Whats wrong here
I keep trying to fucking add the appwrite domains including CNAME and CAA but it keeps failing , this is the exact records i have right now in cf