Hi I do know this isn't fully appwrite related but the api endpoint does use appwrite 3. So the problem is that when I try to access localhost:3001 (and the front end on localhost:3000) and in the fetch include credentials everything works fine. But the problem is when I use a different origin so for example 127.0.0.1:3001 and still front end on localhost:3000 because it wont send the cookies and been working to fix this issue all day and now I am lost...
let test = await fetch("http://localhost:3001/api/checkout/createInvoice?amount=5100", {
method: "POST",
"headers": {
"Content-Type": "application/json",
},
body: JSON.stringify({
"currency": "USD",
"description": "test",
}),
"credentials": "include"
});
test = await test.json();
console.log(test);
``` (Fetch example)
The first img one is the one that failed and the second is the one that works
Ahh cookies are tricky. I'd recommend using something like Ngrok to proxy http requests over https. If the protocal isn't https they wont send if the domain is different (including port). I used ngrok + some secure flags on my cookies to get by.
a_session_${locals.config.appwriteProjectId}_legacy=${sessionToken}; path=/; SameSite=None; Secure;
a_session_${locals.config.appwriteProjectId}=${sessionToken}; path=/; SameSite=None; Secure;
Make sure your "Set-Cookie" header on your sessions request uses SameSite=None; Secure; like ^
The problem is mostly due to 3rd party cookies being blocked
Alright will try that!
Recommended threads
- Using Binary Log with Appwrite
If I can remember correctly appwrite uses mariaDB as the underlying database. If so could I use mariaDB’s binary log to see database operations from appwrite?
- Domain Help
My domain estimately.me is verified in Appwrite DNS but SSL certificate keeps failing with: DNS problem: server failure at resolver looking up A for estimately....
- The deployment is blocked
My domain https://allononeagency.social/