No error page, just a spinner that gives up

Nexus Market onion addresses3 live · same market behind each

nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion

nexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onion

nexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onion

Run 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.

The silent case is the one people find hardest, because a clean error at least tells you something. A spinner that runs out of patience still carries information, and the information is in the timing.

What you see. A blank tab with a loading indicator, running for a long time and ending in a generic timeout or nothing at all.

Read the clock, not the screen

Time the load from the moment you press enter. The number tells you which stage is failing without needing any tooling.

Time before it gives up	Most likely stage	What it points at
Under 20 seconds	Descriptor lookup	The address or its publication. Check the characters first.
20 to 60 seconds	Circuit and introduction	Your path through the network. A new circuit usually clears it.
60 to 120 seconds	Service accepted, never answered	Load at the far end. Another mirror is the fastest move.
Over 120 seconds	Something is answering slowly	Not a failure yet. Give it one more full attempt before switching.

Why no error page appears

Error pages come from your own client when it knows why it failed. When a connection is accepted and then simply stops producing data, there is nothing to report, so the browser waits until its own limit and then gives up quietly. That pattern almost always means the far end is overloaded rather than absent.

What to do

Let one attempt run its full course before judging. Cancelling at ten seconds and retrying repeatedly makes the reading worse and the queue longer.
Try the other mirrors in a separate tab rather than abandoning the first.
If a page eventually appears after a very long wait, stay on it. The slow part is establishing the connection and the rest of the session usually runs at normal speed.

How to read the result

Under a minute, then loads

Normal for a cold connection to a busy onion service. This is what a healthy first load looks like.

Two minutes, then loads

The service is under pressure. Expect the session to be usable but slow. Avoid heavy pages.

Never loads, three attempts

Move to another mirror. You have given this one a fair reading and it is not answering.

Other reachability signals

Reachability

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.

0xF0 · Look elsewhere Reachability

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.

0xF2 · Retry once Reachability

Unable 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.

0xF3 · Retry, then switch

Procedures that apply here

Method