Web Developer
There's a cookie domain issue I keep running into with Appwrite Cloud and a custom domain during local Next.js dev. And it's EXTREMELY frustrating.
My Setup:
- Appwrite Cloud project
- Custom subdomain connected to Appwrite (appwrite.mydomain.com) - SSL is active.
- Next.js app running locally on http://localhost:3000.
- My main app domain and localhost are listed as Web Platforms in the Appwrite console.
- Using the Appwrite Web SDK client-side, configured with the custom domain endpoint.
The Problem:
When I log in from localhost, the a_session_... cookie gets set in my browser, but its Domain attribute is .appwrite.mydomain.com. Because of this, the cookie isn't sent back to my Next.js server running on localhost when I make requests (like navigating to pages checked by middleware or calling server actions). This means server-side session checks fail locally, even though the client-side knows I'm logged in.
I know there are CORS issues and all that in Appwrite. And I know the Secure cookie flag also plays a role with HTTP localhost, but the primary block seems to be the cookie domain. I set up a subdomain and added platforms in the Console just like Appwrite says to do, specifically to avoid issues. But for the life of me, I can't figure out how to get this to work properly.
Question:
Is there a way on Appwrite Cloud to get the session cookie set for the parent domain (e.g., .mydomain.com or even localhost specifically for dev) when authenticating via the custom domain endpoint?
I'm at a loss and don't know what to do. This is extremely frustrating because it seems like I can't do anything in development. Really stuck on how to get validation working reliably during local development with this setup. And I'm not trying to add any complexity or have to jump through hoops just to get this working.
Any help would be much appreciated. Thanks