# Managing Your Node

### Setting Up and Managing a Node

Follow these steps to connect to a node, update its configuration, and use the full set of management tools available in the dashboard.

#### Step 1: Log In

Open the dashboard and log in with your wallet or credentials to access the full set of node management features.

#### Step 2: Go to the Run a Node Page

Navigate to the **Run a Node** page from the main menu. This page is the starting point for connecting to and managing Ocean Nodes.

<figure><img src="/files/b7hwWeJPJDuZMPB2H9AC" alt=""><figcaption></figcaption></figure>

#### Step 3: Overview Ways to Run a Node

\
The page presents the available options for running a node for example, using Docker or the quickstart CLI script. Review these options to understand the deployment methods before proceeding.

#### Step 4: Enter Node Peer ID and Connect

Enter your node's **Peer ID** in the provided input field and press **Connect to Node**. This establishes the connection between the dashboard and your running node.

#### Step 5: Edit Node Config

Once connected, press **Edit Node Config** to open the configuration panel for your node.

#### Step 6: Update Config and Push to Node

Make the desired changes to the configuration values in the editor, then press **Push Config to Node** to apply the updated settings. The node will reflect the new configuration immediately.

#### Step 7: Go to User Profile — Node Owner Tab

Navigate to your **User Profile** and click the **Node Owner** tab. This section is dedicated to node operators and provides a consolidated view of everything related to your owned nodes.

#### Step 8: Overview Statistics and My Nodes Table

At the top of the Node Owner tab you will find a summary of key statistics:

* Total Rewards earned.
* Number of owned nodes.
* Total compute jobs processed.

Below the statistics, the **My Nodes** table lists all nodes you own, along with their status (Online, Warning, Offline), reward eligibility, and performance benchmarks.

#### Step 9: Open Node Details

In the My Nodes table, click on any of your owned nodes to open its **Node Details** page.

#### Step 10: Overview Node Info, Statistics, Benchmark Jobs, Eligibility, and Environments

The Node Details page gives a complete picture of a single node:

* **Node Info**: Peer ID, version, uptime, and network details.
* **Statistics**: Historical performance metrics and job counts.
* **Benchmark Jobs**: Results of automated benchmark runs used to evaluate node performance.
* **Eligibility**: Current reward eligibility status and any conditions affecting it.
* **Environments**: Configured compute environments and available hardware resources (CPU, RAM, GPU).

#### Step 11: Edit Node Config from Node Details

Press **Edit Node Config** within the Node Details page to open the configuration modal. Review the current configuration values, make any necessary changes, and save to push the updated config to the node.

#### Step 12: Send Tokens for Gas Fee

Press **Send Tokens** to open the gas fee panel. Enter the token amount you want to send, confirm, and press **Send**. After the transaction completes, verify that the displayed balance has been updated accordingly.

#### Step 13: Download Logs

Press **Download Logs** to export the node's log file. Use the downloaded logs for troubleshooting, audits, or sharing diagnostic information with support.

***

*For details on how the network monitors your node and benchmarks it for rewards, see the Monitoring & Benchmarking guide.*

### Running Compute Jobs

For details on how to run compute jobs, find resources, and monitor your tasks, please refer to the dedicated Running Compute Jobs guide.


---

# 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://docs.oncompute.ai/ocean-network-dashboard/editor.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.