> For the complete documentation index, see [llms.txt](https://docs.autonomi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autonomi.com/node/guides/how-to-guides/reset-your-nodes.md).

# Reset Your Nodes

Occasionally, you might need to *reset* the Nodes on your device. This might be if they have stopped functioning properly or if it's needed to update their code.

### Resetting with the Node Launchpad

{% stepper %}
{% step %}
**Download** the latest version of the [Node Launchpad](/node/downloads.md)
{% endstep %}

{% step %}
Open the launchpad and **Press** **O** to access the Options screen.
{% endstep %}

{% step %}
**Press Ctrl + R**
{% endstep %}

{% step %}
Type the word **`reset`** and **Press Enter.**&#x20;

*Your nodes will reset and refresh in the background. Sometimes this can take a few moments.*
{% endstep %}

{% step %}
**Press Q** to Launchpad, and then re-open it
{% endstep %}

{% step %}
**Press** **Ctrl + G** to add your Nodes again, and **Press Enter** to start them
{% endstep %}
{% endstepper %}

### Resetting using the CLI <a href="#if-you-are-a-node-manager-cli-user-2" id="if-you-are-a-node-manager-cli-user-2"></a>

Here's the series of commands for advanced users already using the Node Manager CLI tool: `antctl`.\
\
After resetting, and while adding nodes again, note the additional arguments that should be used each time depending, on your circumstances. In particular the `--rewards-address` argument which allows you to attach your [wallet](broken://pages/toNOJmbb6CI5SpEvThmb) address to each node. This is now using the Arbitum One network:

```bash
1. antup update (to make sure you are on the latest version of the Node Manager)
2. antctl reset
3. antctl add (with the following args)
  --count <# of nodes>                                              => If not specified, only a single node is added
   --log-dir-path <path>                                             => optional, path to store the log files.
  --home-network                                                    => optional, if you're behind a NAT/home router/ without port-forwarding
  --upnp                                                            => optional, if you have enabled upnp in your router, mutually exclusive with home-network
  --node-port <single/range of ports>                               => If --home-network or --upnp is not provided, then you have to port-forward a set of ports and provide them here. We accept a single port i.e., 12000 or a range i.e., 12000-12010. The number of ports here should match the number of nodes specified using --count
  --enable-metrics-server                                           => optional, if you want the stats to be displayed inside the launchpad
  --rewards-address <your ethereum wallet address> evm-arbitrum-one => Must be specified at the end, to store your earned ANT.
4. antctl start --interval 2000
5. antctl status --details
```


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.autonomi.com/node/guides/how-to-guides/reset-your-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
