Nexus Entrance / Board index /Which entrance
Nexus addresses three doors, one platform behind them

Your account, balance and orders are the same through all three. Copy rather than retype, and check the signature once you are through.

Door A nexusb2l73qzjn4slhyfxa3jvpolw7fomiz5sgyyefnsdhikaqgborqd.onion
Door B nexusma2iegzo7atzwbrwxhcdopyri3vare2twibldnlc3txqjdeb5yd.onion
Door C nexusabcd6xxpjuftr7i3uohealsg64xtgwrmznkfh3o3rkcf3raxead.onion

An address that opens is not an address that is genuine. The check that settles it takes under a minute.

Locked out of an account

Work through this in order. The likely causes are boring and the order matters, because one of the possibilities changes what you should do first.

Before anythingDo not go looking for a support contact. There is no email, no chat group and no messaging account that belongs to any market, so everything presenting itself that way is impersonation aimed at exactly your situation.

Work through these in order

  1. Confirm you are on a real address. A login that refuses correct credentials is what a clone looks like when it has already taken them. Verify the signature before trying again, not after. If verification fails, stop and treat the credentials as gone.
  2. Try another address. Sessions are shared across the three doors, so a login failing at one and working at another points at that address rather than your account.
  3. Build a new circuit. A slow or dying circuit produces failures that read exactly like rejection, including two factor codes that appear wrong.
  4. Check your clock. Time based codes fail when the machine has drifted, which happens on systems that have been off a while or run isolated. This accounts for a surprising share of these reports.
  5. Check the username, character by character. Not the password, the username. People change the case or a character and then debug the wrong field for an hour.
  6. Wait an hour and try again. Repeated attempts hit rate limiting, and rate limiting looks identical to rejection.

If it was compromised

If you get back in and something is different, or you never get back in and verification failed at step one, treat it as compromised and work in this order. The order matters because it puts the thing an attacker can act through first.

  1. Get in through an address you verified yourself, not the one you were using when it went wrong.
  2. Change the password to something used nowhere else.
  3. Reset two factor and save the new recovery material before closing the page.
  4. Read the message log before anything else. A compromised account is most valuable as a way to talk to people who trust it, so check what was said in your name.
  5. Check open orders and addresses for anything you did not do.
  6. Then deal with the balance. It is the obvious worry and it is not the most urgent one.

What will not help

Thing people tryWhy it fails
Looking for support outside the platformIt does not exist, and everything claiming to be it is targeting people in your exact position
Posting details on a forumIt advertises that you have an account worth attacking and invites private messages from strangers
Trying a dozen passwords quicklyRate limiting, which makes the next hour worse
A new address someone offers youThis is the classic follow up to a lockout and the timing is not a coincidence
Creating a second account to ask about the firstNew accounts have no standing and this does not reach anyone who can act

If none of it works

Recovery without the material you saved at setup is limited and sometimes not possible. That is a real outcome and it is the reason the account page spends most of its length on saving recovery material at setup rather than on password advice. If you are reading this and did save it, use it. If you did not, the honest answer is that the account may be gone, and the lesson transfers to the next one.