nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionRun the check before you sign in. Open these in Tor Browser only. When the login screen loads, compare the onion printed on the page against your address bar, reading from the end. If they differ, close the tab.
You sign in, click one link, and you are at the login screen again. Frustrating, and almost always caused by something on your side that is easy to find.
Where sessions actually get lost
| Cause | How to tell | Fix |
|---|---|---|
| Cookies blocked for the site | Every login works and never sticks | Allow cookies for that onion address only |
| New identity or restart mid session | It happened right after you cleared something | Sign in again and leave it alone |
| Two tabs on different mirrors | Only one tab stays signed in | Use one mirror per session |
| Session actually expired | Hours passed since login | Normal. Sign in again. |
The mirror confusion
Each address is a separate origin as far as your browser is concerned, even though all three reach the same market. A session established on one address does not travel to another. Two tabs open on two mirrors will fight, and the one you are not looking at will usually be the one that loses.
What it is not
A drop is not a sign your account is compromised or being watched. An account under someone else control does not log you out, it stays quiet so you do not notice. Constant logouts point at storage and origins, which is a much duller and much more likely explanation.
While you are in there
If a login screen ever accepts a wrong password without complaint, stop. That is not a session problem, that is a page collecting credentials, and it belongs to the address check rather than this one.
How to read the result
Confirmed storage problem and it is now solved.
Origin collision. One mirror per session and it goes away.
Use a different mirror. Something at that address is not issuing sessions correctly.
Other integrity signals
The address on the page is not the address in your bar
The one signal that ends a session rather than starting a diagnosis. How the check works on a Nexus mirror and why it cannot be faked.
IntegrityThe protection gate never lets you through
Anti flood gates on a Nexus mirror can loop forever. What causes the loop, why hammering makes it permanent and how to get past it.
IntegrityThe page loads but half of it is missing
Unstyled pages and dead buttons on a Nexus mirror usually mean the assets did not arrive, not that the page is a fake. How to tell the two apart quickly.
Procedures that apply here
Choosing which of the three mirrors to use
The three Nexus addresses reach the same market. How to pick between them sensibly and why the fastest one today may not be tomorrow.
MethodHow to take an honest reading of a mirror
A repeatable way to measure whether a Nexus mirror is slow, broken or fine, without tooling and without fooling yourself.
SafetyConfirming you are on a real Nexus mirror
The check that separates the market from a convincing copy, why appearance proves nothing and what to do if the check fails.