> For the complete documentation index, see [llms.txt](https://docs.accumulatenetwork.io/accumulate/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.accumulatenetwork.io/accumulate/nodes/debugging-node-issues.md).

# Debugging node issues

### The node is not responding to API requests

1. Run `netstat -alpn | grep <port>` to check if Accumulate is or is not listening on the relevant port. A response like `tcp6 0 0 :::16695 :::* LISTEN 20355/accumulated` indicates that Accumulate **is** listening.
   * If Accumulate is listening, something is blocking or interfering with connections to the node. If you can connect to any port (including SSH or HTTPS), the issue is likely an incorrect firewall configuration.
   * Otherwise (if Accumulate is not listening),
2. Check if Tendermint is still catching up. Open `http://<your-node>:<tendermint-rpc>/status` in your browser, or make the equivalent RPC call.
   * If you get no response, use `netstat` to check if its listening. If it is listening, see above.
   * If it is not listening, wait for a minute to ensure the node has booted. If there's still no response, ask for help.
   * If you get a response and `catching_up` is `true`, wait for it to finish catching up.
   * If you get a response and `catching_up` is `false`, ask for help.

### Prometheus is not responding to requests

When running a DNN and BVNN in dual-mode, the BVNN's Prometheus exporer is disabled. Because of how Tendermint initializes Prometheus ([see here](https://github.com/tendermint/tendermint/issues/7076)), the Prometheus exporter cannot be enabled for both nodes. If neither the DNN's nor the BVNN's exporter are responding to requests, see [#the-node-is-not-responding-to-api-requests](#the-node-is-not-responding-to-api-requests "mention").

### Port numbers

The base port for the testnet and mainnet is 16591. All of the node ports have a fixed offset from the base port.

<table><thead><tr><th width="249">Service</th><th>DNN</th><th>BVNN</th></tr></thead><tbody><tr><td>Tendermint P2P</td><td>0</td><td>100</td></tr><tr><td>Tendermint RPC</td><td>1</td><td>101</td></tr><tr><td>Prometheus</td><td>3</td><td>103</td></tr><tr><td>Accumulate API</td><td>4</td><td>104</td></tr></tbody></table>


---

# 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.accumulatenetwork.io/accumulate/nodes/debugging-node-issues.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.