Nexus URL

Nexus Market not loading: nine fixes, fastest first

The market being down is rarer than people report, because most "down" reports are one of the nine below. Work the list top to bottom. Each fix takes under a minute, and together they explain the large majority of stuck loads.

The fixes

01Re-paste the address. Compare the last six characters.Start with the thing that is wrong half the time: the address. One transposed character loads a different onion, many of which are dead, parked, or someone else's project with a very slow first page. Paste fresh from the mirrors page and read the final six characters in your bar against the source before you wait another minute.
02Try the other two addresses.The three entry points are separate onion identities in different regions. A circuit that cannot reach one of them will often reach the next in seconds. If two of three fail and one loads, your path to the failed two is the problem, not the market. Keep the working one in your rotation.
03Wait a full minute without refreshing.Tor builds a circuit through three relays before it even starts talking to the onion. On a busy line that is 30 to 60 seconds of nothing. Every refresh tears the circuit down and restarts the build, so an anxious refresh habit looks exactly like a dead market. One patient minute, then judge.
04New identity, then reload.Ctrl+Shift+I on desktop. A fresh identity means a fresh circuit and a clean entry into the network. If the previous session was slow, the new one usually is not. This is also the fix for a circuit that was built during a congested window and cached your bad luck.
05Check that Tor itself is connecting.The onion icon in the address bar shows the circuit state. If Tor itself shows "not connected" or is cycling relays, the market is the least of your problems. Close and reopen the browser first. If Tor connects to normal clearnet sites fine but onions stall, the problem is on the onion side of the path, and the other two addresses are your next move.
06Your network may be blocking or throttling relays.Schools, offices, and some national networks filter the port ranges Tor uses. The symptom is a browser that "connects" but loads everything at the speed of a dial up. The fix is a bridge: Settings, then Advanced, then bridge, then let Tor suggest a pluggable transport. Set it once, and the filtering stops being your problem. This is the fix for the "it was fine on my phone" reports, because phone networks rarely filter and fixed lines sometimes do.
07On Android, give it more time and less multitasking.The mobile Tor Browser is slower at circuit building and more sensitive to the phone moving networks. Lock the screen for the minute instead of refreshing, and make sure the phone is not juggling a wifi to cellular handoff mid load. The market's own check page allows up to 30 seconds and the captcha a full 60; mobile loads sit comfortably at the top of those windows, which is by design, not by bug.
08JavaScript is on. It has to be.Both the browser check and the DDoS captcha are scripts. A browser with scripts disabled, or with an extension stripping them, sits on the check screen forever. Security level Standard in the Tor Browser leaves scripts on. If you raised the level to Safer or Safest while debugging, that is your stuck page. Back to Standard, new identity, reload.
09It is down, briefly. Come back in an hour.Entry points go down for maintenance and under attack, the way any public endpoint does. If all three addresses, on a fresh identity, with a working Tor connection, all sit at the same wall for an hour or more, the market is the variable. There is no feed to watch and no badge to trust, which is exactly the topic of the status page. The practical move: close the tabs, make a new identity later, and try again. Markets in this category come back more often than they close.

What "not loading" is not

It is not your account. The market's entry point does not know or care whether you have an account; the checks run before any login exists in the picture. It is not your coins. Nothing in the loading path touches your wallet. And it is not fixed by logging out of the market, because you were never logged in during the load.

A quick decision tree