Three addresses, one market. Same account, same orders, same balance behind each one. No accounts, no forms, nothing collected

HomeSignals › Uploads and large pages stall out

Uploads and large pages stall out

When image uploads to a Nexus mirror stall at a percentage or big pages stop halfway, the circuit has run out of usable bandwidth.

Group
Latency
First move
New circuit
How long to give it
Do not wait
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.

Small pages fine, anything substantial dies partway. This is the clearest throughput signal there is, and unlike the others it does not improve by waiting.

What you see. An upload that sits at a fixed percentage, or a long page that renders halfway and stops.

Why waiting does not help here

Latency problems clear because queues drain. A throughput problem is a ceiling, not a queue. If the narrowest relay in your path can only push a trickle, another ten minutes buys you a slightly larger trickle and nothing more. The fix is a different path.

What to do, in order

  1. Request a new circuit for the site and retry the upload from the start.
  2. If the second circuit is also thin, try a different mirror, which forces an entirely new path on both halves of the connection.
  3. Shrink what you are sending. A smaller image is not a workaround, it is the correct answer on a network with these constraints.

Before you retry an upload

Check whether the first attempt partially landed. Sending the same attachment three times because each looked stalled leaves a mess that somebody has to sort out, and on a dispute it looks worse than the original problem.

A realistic expectation

Onion services are not built for bulk transfer. Photographs sized for a phone gallery are large by this network standard. Resizing before upload turns a five minute gamble into a ten second certainty.

How to read the result

Completes slowly

Fine. Slow is the normal state for anything sizeable here.

Stalls once, works after a new circuit

Confirmed thin path. Nothing wrong with the market or your account.

Stalls on two circuits and two mirrors

The far end is shedding large requests under load. Come back later rather than retrying.

Other latency signals

Procedures that apply here