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.
This is the error people see most and misread most. It does not mean the market is gone. It means your Tor client asked the network where that address lives and got nothing back.
What is actually happening
Every onion service publishes a small record saying which relays will accept an introduction on its behalf. That record is called a descriptor and it lives on a rotating set of directory relays. When you open an address, your client works out which relays should be holding the descriptor today and asks them. This error means every one of those asks came back empty.
The three reasons, in order of likelihood
- The address is mistyped or truncated. One wrong character is a completely different service that nobody has ever published a descriptor for.
- The service stopped publishing. That happens during maintenance, a move, or a genuine shutdown, and it looks identical from outside.
- Your client picked directory relays that are having a bad day. This is the rarest of the three and the only one a retry fixes.
What it does not mean
It does not mean you have been blocked, flagged or singled out. The lookup fails before anything on the service side has any idea you exist. It also says nothing about the other two mirrors, because each address publishes its own descriptor independently.
What to do
- Compare the address in your bar against the list on this site character by character, especially the last eight.
- Try the other two mirrors before anything else. If one of them opens, the market is up and that one address is not publishing.
- If all three give 0xF0, wait rather than hunting. Searching for a replacement while every known address is quiet is exactly how people land on a cloned one.
Timing
A descriptor lookup fails fast, usually inside fifteen seconds. If you are staring at a spinner for a minute and then get this page, the slow part was circuit building and not the lookup.
How to read the result
The other two almost certainly work. Switch and carry on. This is the normal case and it is why three addresses exist.
One address is answering and it is carrying everyone. Expect it to feel slower than usual and be patient with it.
Stop. Do not search for a new address. Come back in a few hours and use only the addresses you already had saved.
Other reachability signals
Onionsite 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.
ReachabilityUnable 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.
Procedures that apply here
Confirming 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.
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.
IncidentWhat to do when none of the three answer
How to tell a service wide outage from a problem on your side, and the one action that turns an inconvenience into a loss.