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.in
Thendocker compose down
anddocker compose up -d
to 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
- I recently applied for the free plan und...
I recently applied for the free plan under the GitHub Student Developer Pack. However, my billing status still shows $15, and it mentions that this amount will ...
- How to Avoid Double Requests in function...
I'm currently using Appwrite's `functions.createExecution` in my project. I want to avoid double requests when multiple actions (like searching or pagination) a...
- Bug Report: Appwrite Console UI Issue on...
Steps to Reproduce: - Navigate to any collection page in the Appwrite console UI. - Open the menu and click on "Create Collection." - Observe that the dialog to...