> For the complete documentation index, see [llms.txt](https://zugchain.gitbook.io/zugchain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zugchain.gitbook.io/zugchain/validator-operations/troubleshooting-and-faq.md).

# Troubleshooting & FAQ

### <mark style="color:$primary;">Common Troubleshooting</mark>

#### <mark style="color:$warning;">1. I have 0 Peers" in the logs</mark>

Your firewall is absolutely blocking the connections. Please re-visit the Network & Firewall step. Ensure ports `30303`, `13000`, and `12000` are open internally (e.g., UFW) AND externally on your Cloud Provider's website (Security Groups/VPC).

#### <mark style="color:$warning;">2. Sync Warnings (Execution client is not syncing)</mark>

During the very first day, your node must download the entire history of the blockchain. You will see errors like "Beacon node is not respecting the follow distance" or "No responsive beacon node found". This is perfectly normal! Be patient. Once the history sync reaches 100%, these errors will vanish automatically.

#### <mark style="color:$warning;">3. "Waiting for deposit" OR "No active keys"</mark>

Your node is running perfectly! However, the network either hasn't seen your 32,000 ZUG deposit yet, or your keys are in a queue waiting to be activated. If you haven't made your deposit transaction yet, head over to the Launchpad to complete it. Otherwise, simply wait for the network to activate your node (this can take up to a few hours depending on the queue).

{% hint style="info" %}
Official Deposit Contract Address: `0x00000000219ab540356cBB839Cbe05303d7705Fa` *Always verify this institutional hex identifier before making any deposits!*
{% endhint %}

{% hint style="success" %}

> 💬 Still need help? *Open a Ticket in our* [*Official Discord Server ↗*](https://discord.com/invite/dV2sQtnQEu)
> {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://zugchain.gitbook.io/zugchain/validator-operations/troubleshooting-and-faq.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.