Not sure if that's necessary...if account.get() is successful, the user has a valid session. Otherwise, they don't
Oh ok, I'll try, thanks for the info, I'll be back I'll try
I changed getSession("current") to get(), but the effect remains the same :/
You might have a problem with 3rd party cookies. Either enable 3rd party cookies or set up your app and Appwrite such that Appwrite is a subdomain of your app
Indeed, on Chrome it works correctly, but not Firefox :/
It's a bit complicated to put a subdomain on the same domain as "localhost" lol
Look for 3rd party cookie settings
You could update your hosts file to have a local domain
It's actually a good idea ^^
Well, in the end, the problem was just the cookies... Lol Thank you for your help ^^
Like this, is it correct?
Do you know if there is a way to bypass the CORS error?
Because the request is made from the Appwrite SDK, so I don't have control over the headers.
What error are you getting?
Did you browse to Appwrite.localhost and accept the self signed certificate?
Firefox ignores the hosts file despite the recommended settings. I will search again
Okay good, browsers don't like domains like ".localhost"
You can use any domain since it's just local testing
According to this answer, some local domains are not valid.
But let's move on, thanks to your solutions I was finally able to have a functional application :D
Sorry I mean use something like example.com
Ohhh okay
[Solved] Nuxt 3 | OAuth callback URL
[SOLVED] Nuxt 3 | OAuth callback URL
Recommended threads
- Appwrite SSL Certificate Failure
Hello, I need help releasing a stuck domain. My Domain: adilnaib.engineer My Project ID: 68fe0aee001e999b5d71 Error: Failed to add domain to Fastly: {"msg":"B...
- [BUG] I'm facing an issue while creating...
Here’s what’s happening: When I try to create a new Web app on my Appwrite console (backend.keplr.in), the browser console shows multiple errors: Uncaught (in...
- Sites: Old deployment gets requests even...
Hi team, I use Sites to host a Next.js web app and it serves from old deployment for many hours. Is this expected? I thought it would serve from new deployment ...