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.
Descriptor found, introduction attempted, handshake did not complete. Of all the reachability errors this is the one most likely to be your side of the connection.
Where it breaks
Connecting to an onion service takes a small negotiation. You pick a relay to act as a meeting point, tell the service about it through one of its introduction points, and both sides build circuits to that meeting point. This error means the negotiation started and did not finish. Any of the six or so relays involved can be the reason.
Why your side is the usual suspect
A service under load fails at introduction and reports it consistently. A single unlucky relay in your own path fails intermittently, which is what most people actually see. If the same address opens on the next try, or opens after you request a fresh circuit, the fault was in the path and not at the far end.
What to do
- Retry once. Different relays get chosen and the problem often evaporates.
- If it repeats, request a new circuit for the site from the browser menu and try again.
- If it still repeats, try another mirror. Two addresses failing the same way points away from your path.
A note on timing
This error takes longer to appear than the other two because the client waits for a handshake that never lands. A long wait ending in 0xF3 is normal for this error and does not mean anything extra.
How to read the result
A relay in your path had a bad moment. Nothing to read into it, and nothing to change.
Get a new circuit for that site before deciding anything. Most repeats stop there.
Your Tor client is having a wider problem. Restart the browser fully, which rebuilds guards and circuits from scratch.
Other reachability signals
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.
ReachabilityOnionsite 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.
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.
Procedures that apply here
Requesting a new circuit, and when it actually helps
The single most useful control in Tor Browser for onion problems, what it does, what it costs and which symptoms it fixes.
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.
MethodChoosing 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.