
I’m using Appwrite for my web app and noticing that after ~15 minutes, my user session suddenly expires—calls like account.get() start returning 401 Unauthorized.
Here’s what I’ve confirmed so far:
Short-Lived JWT: I’m aware Appwrite’s JWT has a 15-minute expiry, but even if I try account.createJWT() after 15 minutes, it fails because the entire session is gone.
Session Cookie: Looking in the browser, my app’s session cookie is set to expire a year in the future, yet Appwrite still terminates the session around the 15-minute mark.
Has anyone dealt with this mismatch where the cookie’s “Expires” date is far in the future, but Appwrite ends the session after ~15 minutes anyway?
How can I configure (or refresh) the session so it remains valid beyond 15 minutes without forcing the user to re-log in?
my edge case I'm running into is when the user who wandered around the web app successfully steps away for 15+ minutes then comes back, and clicks a button that sends a request to my backend (with JWT) has that request fail.
the only trick I found to make it work again is to manually refresh the whole page/webapp at which point everything works again.
Recommended threads
- Auth Error
"use client"; import { useEffect } from "react"; import { getSessionCookie } from "@/actions/auth"; import { createBrowserSessionClient } from "@/lib/appwrite-...
- Cannot connect to SMTP in AppWrite - set...
This used to work and then at some point it stopped. One thing that happened in that time was moving my application to Vercel. I have read on another thread t...
- Prevent modifying specific attributes
How do I prevent user to only to be able to modify some of the attributes. Document level security gives full access to update whole document, what are the wor...
