Troubleshooting

The handful of things that actually go wrong, and what each one usually means.

The reply never arrives

"Nymbot is still working on that message." A long Pro reply, or a repository task, can outlast the request that asked for it. The answer is being generated and is held for you; send the same message again and you collect it rather than paying for a second one.

"Could not fetch your encrypted message from the relays yet." Your wrap had not propagated when the worker went looking. Try again — nothing was charged.

Nothing at all. Check the connection indicator. If the app cannot reach the relays it cannot publish your message, and a network that blocks WebSockets — some corporate and hotel networks — will stop it dead.

The balance looks wrong

?balance asks the server rather than reading a cached number, so start there.

A payment that settled but did not credit is usually a claim interrupted between the two. Reopen the purchase and it completes; the claim is idempotent, so you cannot be credited twice by retrying.

If you are in anonymous mode, remember the throwaway key has its own balance. ?balance shows that one while the mode is on, and your nym's balance is untouched behind it.

A reply that cost more than you expected was probably a long Pro reply — those scale with length — or a repo task that used several model calls. The app reports both.

A server run is charged separately from the reply that asked for it, and deep research and Team mode are metered across many model calls. Each shows what it cost. While one is going, its maximum is held, so your free Pro balance looks lower until it settles.

A conversation is missing

On a new device, history is restored from the relays, which takes a moment and depends on the relays still holding those wraps. Give it time before concluding it is gone.

If you are signed in with a different key than the one that had the conversation, you will not see it and cannot — it is encrypted to the other key. Check the nym in the header.

A cleared conversation or a device wipe is not recoverable by anyone.

The repository will not connect

"That does not look like a valid token." The token format did not match the provider you chose. GitHub, GitLab and Gitea all issue different shapes.
The repository list is empty. The token is valid but not scoped to any repository, or scoped to an organization that has not approved it.
It connects but cannot write. Writes are off by default — ?git writes on — and the token also needs write scope at the provider.
It works on one device and not another. Tokens sync between your devices, so give a new device a moment after signing in. A repository marked as having no token was disconnected on one of your devices, or was connected from an older version of the app that kept tokens on one device. Add the token again and it syncs from there.

A server run did not start

"The price went up since this was shown." The price of a server run follows the Bitcoin price, and it moved between showing you the price and starting the run. Nothing ran and nothing was charged. Check the new price and run again.
Not enough Pro credits. The whole maximum has to be free in your Pro balance before a run starts. The app opens the Pro top-up.
"Another server run of yours is still going." One run at a time for each key. Wait for it to finish, or press Stop on it.
"Slow down — too many requests." Try again in a minute.
"Server runs are not available right now." They are switched off, or the servers could not be reached. Nothing was charged.
"Stopped at the time limit." The run used its whole time limit. Choose a longer one, or ask for code that does less at once.
The connection dropped. What arrived is shown. The run is settled on the server even if the app lost the connection, and your balance shows the charge.
In a repository, "That request has expired." An approval card was left too long. Ask again and Nymbot starts fresh. A repository over 60 MB, packed, is too large for a server run.

A connector will not connect

"Connectors must use https." or "That address is local or private." The worker can reach only public https addresses, so a server on your own machine or network cannot be used.
"Put credentials in the token or header fields, not in the URL." Move the token out of the address and into the connector's authentication.
"The connector could not be reached." Check the address and the token. The server has to speak MCP over HTTP.
"Its secret is on another device." The connector's token has not reached this device, usually because it was added from an older version of the app that kept secrets on one device. Edit it and add the secret here.
A reply never uses it. Connectors need a Pro model pinned, a chat can have at most three turned on, and a tool you unchecked is never offered to the model.

Locked out of an encrypted identity

Identity encryption has no recovery path. That is what makes it worth having, and it means a forgotten passphrase, a lost passkey or biometrics that no longer work on the device end that copy of the identity.

Forgot your passphrase? or Lost your passkey? on the unlock screen offers, after a warning, to delete the key and everything else Nymbot keeps on the device, and start over.

If you backed up your nsec, reinstall and sign in with it. If you did not, the identity is gone — which is the moment everyone learns why the backup is the first thing this knowledge base tells you to do.