Fix · Sign-in and accounts

Users get logged out after a refresh or a page change

Blocks your work

What you may see

I log in, move to another page and I am logged out
The server sees no user though the browser shows one

Most likely cause

The login is kept in a cookie; if the cookie is not set, not sent to the server, expires too soon, or the server code cannot read it, the user looks logged out.

Check first (about two minutes)

In the browser's Application tab, after logging in, is there a session cookie for your site?
Does it break only on the live site or only on one browser?

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who knows sign-in, sessions and user accounts, and explains them to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

THE PROBLEM
Users get logged out after a refresh or a page change

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The login is kept in a cookie; if the cookie is not set, not sent to the server, expires too soon, or the server code cannot read it, the user looks logged out.

DO THESE STEPS, IN THIS ORDER
1. Find how sessions are created and read on the server (which library, which helper), and which routes check them.
2. Check cookie settings: secure on https, the right domain and path, SameSite lax, and a sensible lifetime.
3. Make sure the session is refreshed in the one place the library documents (often a middleware), and that responses carry the updated cookies.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- After login, a refresh and navigation keep the user logged in for the expected time, on phone and desktop.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not store the login token in localStorage to work around it.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Find how sessions are created and read on the server (which library, which helper), and which routes check them.
Check cookie settings: secure on https, the right domain and path, SameSite lax, and a sensible lifetime.
Make sure the session is refreshed in the one place the library documents (often a middleware), and that responses carry the updated cookies.

Do not do this

Do not make cookies readable by page scripts to "fix" it.
Do not store the login token in localStorage to work around it.

Try another entry