Nexus Market URLNexus Market

Nexus troubleshooting

Fixes for the common problems.

Verified Nexus Market onion linkschecked 2026-09-01
1
2
3
All addresses resolve to the same market. Before entering a password, check the address against the one the login captcha prints. See verifying the address.

Most Nexus problems have simple causes.

Cannot connect or slow

Almost always your Tor circuit or a temporary flood, not the market. Request a new circuit and retry, or switch to another address on this page. If all three stall across circuits for several minutes, wait a short while, because floods pass.

Captcha address does not match

Stop. That is the phishing signal. Do not type anything, close the tab, and copy a verified address fresh. If a deposit has not shown, it is usually waiting on confirmations, or an underpaid Bitcoin fee, and you sent to the address from the correct order.

Read the error rather than the symptom

Not found means the lookup failed before any connection existed, so reloading changes nothing and the address or its publication is the issue. Disconnected means the record was found and the service did not answer, often during a restart or under load, and that frequently clears in minutes. A connection failure usually points at a relay in your own path. Three different failures at three different stages, all reported as the site being down.

Time a silent failure

When there is no error at all, the clock tells you which stage broke. Under twenty seconds points at the lookup. Twenty to sixty at your circuit and the introduction step. Over a minute with nothing coming back points at load on the far end. No tooling required, just do not cancel at fifteen seconds, because an abandoned attempt produces no information.

Text arrives and images do not

That is throughput rather than reachability. Your circuit has acceptable latency and poor bandwidth, which are separate properties. Waiting fixes queues and does nothing about a ceiling, so a new circuit for the site is the only real fix and it costs a fresh cold load.

The session freezes partway

A relay dropped and the circuit is being repaired, which usually completes within a minute. Reloading cancels the request that was about to succeed and queues a new one behind the same repair. On a payment or an order step, never resubmit during a stall. Wait for the page to settle and check the order state before touching anything.

Logged out on every page

Almost always cookies blocked for the address, or two mirrors open at once. Each onion address is a separate origin as far as your browser is concerned, so a session on one does not carry to another and two tabs will fight. One address per session and the problem disappears.