Anubis Market Troubleshooting
Fixes for the problems that actually happen on Anubis Market, a mirror that will not open, a deposit that is not confirming, a captcha that loops, and a balance that looks wrong. Each fix is the specific check, not the general advice, and the one that matters most is the address check, because it stops a clone before a password is typed.
The problems and the fixes
6 issuesA mirror will not open
Give a single attempt a full minute before judging it. A cold connection to a hidden service crosses roughly six relays with no caching anywhere, so tens of seconds of nothing is the normal state rather than a fault. If it still will not open, move to the next mirror rather than reloading the same one, because a reload rebuilds the same failing path. If all three fail, open any other onion service you know. That single test separates a problem in your own client from a problem at the market, and it takes twenty seconds. If nothing onion works, restart Tor Browser completely. If other onions work and these do not, wait rather than hunting, because an outage consumes nothing: escrow keeps holding, orders keep their timers, and a balance does not evaporate because a storefront was quiet for an afternoon.
A deposit is not confirming
The address is not the cause. The payment is happening on a blockchain that has no idea which onion you signed in through. Check three things, in order. The coin reached the required number of confirmations on its own chain, which you can verify in your wallet independent of the market. The address you sent to is the one the market generated for the order, checked character for character. The amount you sent is the amount the order required. If the coin confirmed on-chain and the market does not show it, the fix is to open a support ticket with the transaction hash, not to resend, because a resend to the same address is a second deposit, not a retry.
The captcha loops
The six-tile captcha has decoy input fields whose names rotate on every page load. If the captcha keeps resetting, you are filling a decoy field, or a script is filling every input on the page. Solve the tiles in the visible field only, and do not fill the decoy fields. If a browser extension is present, disable it for the session, because an extension that auto-fills forms is the most common cause of a captcha that will not hold. The full login flow is on the login page.
The balance looks wrong
Check the coin, not the number. A balance shown in one coin is not the same as a balance shown in another, and the market shows the balance in the coin you are viewing. If you deposited in Monero and are viewing the Bitcoin balance, the Monero is not missing, it is in the other coin. Switch the coin view and the balance is there. If the balance is wrong in the coin you deposited, open a support ticket with the transaction hash. The deposit address is fresh per order, so a balance that is wrong in the deposited coin is a deposit the market has not credited, not a coin that moved.
I signed in on one mirror and I am signed out on another
That is the normal state, not a fault. Your browser treats each mirror as a separate site, so signing in on one leaves you signed out on the others. Your account, balance, and open orders do not move between them. Sign in again on the mirror you moved to and both are there. The cost of switching is a fresh connection, which is tens of seconds, plus signing in again. The detail is on the mirrors page.
The address in my bar does not match the login screen
Do not enter a password. Close the tab without typing anything. Go back to the trusted source, copy the address again, and open it fresh. Do not try to fix the address by hand, and do not reload the same tab, because a reload rebuilds the same failing path. A one-character difference is a clone, not a slow mirror. The full method is on the verify address page, and how the clone operates is on the phishing page.
The one fix that covers most of these
Check the address before you type a password. A mirror that will not open is usually the circuit, not the address, and the fix is to move to the next mirror, not to reload. A deposit that is not confirming is usually the coin, not the address, and the fix is to check the chain, not to resend. A captcha that loops is usually a decoy field or an extension, not the market. The address check stops the problem that actually takes an account, and it takes ten seconds.
What not to do during an outage
Do not search for a replacement address. The search is the moment a clone is built for. Keep the mirrors saved somewhere you can reach without a search engine, and the outage is an inconvenience, not a risk. The detail is on the phishing page.
The order of checks
Address first, then coin, then the specific problem. The address check stops a clone. The coin check stops a balance that looks wrong. The specific fix is the one that is left after those two. Most of the problems on this page are the first two, not the third.