SID Session
sid-session means your dashboard session has ended. It is not an account problem or a data problem. Log in again with your access key and your dashboard picks up exactly where you left it.
What causes a session to end
Your dashboard session is a time-limited credential stored in a cookie. When you log in with your access key, the server issues a session token and sets it in your browser. The session is valid for a period of inactivity — if you do not interact with the dashboard for a set duration, the session expires automatically. Opening the dashboard in a new tab or navigating to it after a long idle period presents the login form because the session token is no longer valid.
Sessions also end when you log out explicitly, when the server is updated and active sessions are invalidated, or when your browser clears cookies — which can happen after a browser update, a privacy-clearing action, or a settings change that removes stored cookies. In each case, sid-session is the system telling you that the session token it received was not recognized.
Regenerating your access key immediately invalidates all active sessions across all devices. If you or anyone with access to your admin panel regenerated the key, every browser that had an active session will encounter sid-session on its next dashboard request. Log in with the new key on each device to restore access.
How to log in again
Go to statelessid.com/login. Enter your access key — the 32-character hexadecimal string from your password manager. Submit the form. A valid key issues a new session and forwards you to the dashboard. Your data, your sites, and your settings are unchanged. The session expiry is a login state, not an account state.
If the login form clears without logging you in, the key submitted did not match an account. This is a different problem from sid-session. See the cannot-log-in and site-key-vs-access-key articles to work through the login failure. sid-session resolves cleanly with a correct key; if the key itself is the problem, the session error is secondary.
Why sessions are time-limited
An indefinite session would mean that anyone with access to a device where you had previously logged in would have permanent access to your dashboard. A session that expires after inactivity limits that window. If you logged in at a library computer, a shared workstation, or a borrowed device and then walked away, the session expiry is the backstop that prevents the next person at that device from opening your dashboard.
Session expiry is also protection against an old browser tab that was left open and forgotten. A tab in a browser you no longer actively use can persist for days or weeks. A session that expires on inactivity means that old tab no longer has a valid credential, even if the tab is still open in memory.
If you see sid-session immediately after logging in
A sid-session error that appears before you have had a chance to use the dashboard — immediately after what appeared to be a successful login, or on the first page load after submitting the login form — can indicate a cookie problem in the browser. If the session cookie is not being set or persisted, every request to the dashboard will appear to be an unauthenticated request.
Check whether your browser is configured to block third-party cookies or to block all cookies. The session cookie for statelessid.com is a first-party cookie set on the statelessid.com domain, so blocking third-party cookies should not affect it — but some aggressive privacy settings block all cookies, first-party included. Temporarily relaxing cookie settings for statelessid.com and logging in again tests whether this is the cause.
Also check whether a browser extension is intercepting or deleting cookies for this domain. Cookie-clearing extensions that run on each page load can remove the session cookie before the next dashboard request has a chance to send it. Test in a private window with extensions disabled to isolate extension interference.
Troubleshooting
If you log in and sid-session reappears after a very short time, the session timeout may be shorter than expected, or the session cookie is being cleared between requests. Open the browser developer tools, go to the Application tab (Chrome) or Storage tab (Firefox), and look for cookies set on statelessid.com. If the session cookie disappears between page loads, something is deleting it. Check for extensions that clear cookies automatically or browser settings that limit cookie persistence.
If sid-session appears across multiple browsers simultaneously and logging in on each one fixes it only briefly, a recurring session invalidation may be happening at the server level. This is uncommon but can occur during account configuration changes or when the access key is regenerated. Contact support if the pattern repeats after several clean login attempts across different devices.