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.
Twelve signals, grouped by where they break. Reachability signals end in an error page. Latency signals end in a page that arrives too slowly. Integrity signals mean the page arrived and something about it is wrong, and one of them is a reason to stop rather than diagnose.
Reachability
4 signalsWhether a circuit to the service can be built at all. These are the signals that end in an error page rather than a slow one.
Onionsite Not Found
What the 0xF0 error means when a Nexus mirror will not open, why retrying rarely helps, and which of the three addresses to try next.
0xF2Onionsite Has Disconnected
The 0xF2 error means the descriptor was found but the service did not answer. Why that is a better sign than it looks and how long to give it.
0xF3Unable to connect to the onionsite
The 0xF3 error sits between a lookup failure and a real page, and it usually says more about your circuit than about the Nexus mirror.
ReachabilityNo error page, just a spinner that gives up
When a Nexus mirror produces no error at all and the tab simply spins, the useful information is in how long it spins before quitting.
Latency
4 signalsThe page arrives, eventually. These signals tell you where the time is going and whether waiting will help.
Long wait before anything appears
Time to first byte on an onion service includes six relays and a rendezvous. What is normal for a Nexus mirror and when the number stops being normal.
LatencyText lands fast, images crawl
Why listing photos on a Nexus mirror lag well behind the page text, what that says about your circuit, and when to stop waiting.
LatencyThe session freezes partway and then resumes
Pauses in the middle of a working Nexus session usually mean a relay dropped and the circuit is being rebuilt. Why waiting beats reloading.
LatencyUploads and large pages stall out
When image uploads to a Nexus mirror stall at a percentage or big pages stop halfway, the circuit has run out of usable bandwidth.
Integrity
4 signalsThe page arrives and something about it is wrong. These are the signals worth stopping for rather than retrying.
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.
IntegrityLogged out on every page you open
Constant logouts on a Nexus mirror are almost never the market. Where the session is actually being lost and what to check first.
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.
How to use this reference
Find the signal that matches what you are actually seeing rather than what you assume is happening. Most wasted time comes from deciding a mirror is down and reloading, when the error on screen said the failure was in the lookup and no amount of reloading was ever going to change it.
Each entry ends with three readings, because the same signal means different things depending on whether it appears on one address or all three. That distinction is usually the whole answer.