# FAQ & Error Messages

***

## Common error messages

### ❌ Transaction failed — Slippage exceeded

**What happened:** The token price moved between when the bot prepared the buy and when the transaction was executed.

**Fix:** Increase the **Slippage** in the Sniper configuration (15–20% is recommended).

***

### ❌ Transaction failed — Insufficient balance

**What happened:** Your wallet did not have enough SOL to cover the buy and network fees.

**Fix:** Deposit more SOL into your wallet. Always keep a bit more than your buy budget to cover fees (\~0.003–0.005 SOL per transaction).

***

### ⚠️ Token skipped — Vibe Score too low

**What happened:** The token did not reach your minimum Vibe Score threshold.

**Fix:** This is normal — the filter worked. If you want to buy more tokens, lower the minimum Vibe Score in the configuration.

***

### ⚠️ Token skipped — Bundle detected

**What happened:** The Bundle Check detected suspicious activity around this token.

**Fix:** This is a normal protection. If you want to disable this filter, go to **🔍 Advanced Filters**.

***

## Frequently asked questions

### 🔑 What is a Nonce Account?

On Solana, every transaction needs a recent blockchain reference to be valid — this is called a **blockhash**. The problem: this blockhash expires very quickly (about 2 minutes). If your transaction is prepared too early or sent too late, it is rejected.

The **Nonce Account** solves this problem. It is a small Solana account that stores a "frozen" reference that never expires. The bot can prepare your transaction in advance using this nonce, and send it at the right moment without risking expiration.

**In short:** the Nonce Account allows the bot to be ready to buy instantly without wasting time fetching network data at the last moment. This is one of the reasons Dark Entry Bot is so fast.

> The Nonce Account is created and managed automatically by the bot. You don't need to do anything. If a problem occurs (rare), use the **Reset Nonce** option in the **👛 Wallet** menu.

***

### Can the bot buy several tokens at the same time?

Yes. Each signal is processed independently. If multiple tokens pass your filters at the same time, multiple buys can be executed simultaneously.

***

### Are my positions lost if the bot restarts?

No. All positions and their protections are saved and restored automatically on restart.

***

### My copytrade is not triggering — why?

Check the following:

* Is the copied wallet **active** in your list?
* Has the copied wallet reached the **Max Consecutive Losses** limit?
* Does the purchased token pass your filters (**Max Market Cap**, **Token Age**)?
* Do you have enough **SOL** in your wallet?

***

### My rugger is not triggering — why?

Check the following:

* Is **Rug Snipe** enabled in the rugger's settings?
* Is the rugger launching the token from the wallet you are monitoring, or from a different one?
* In **Main Wallet** mode, do your amount ranges match the actual transfers?

***

### My subscription was not activated after my payment

**Fix:** The detection window is 5 minutes. If you paid after this delay, contact the bot operator with the signature of your Solana transaction.

***

### How do I withdraw my SOL if my subscription has expired?

You can withdraw your funds at any time, even without an active subscription. Go to **👛 Wallet → Withdraw**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dark-entry.gitbook.io/dark-entry-docs/bonus/erreurs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
