> For the complete documentation index, see [llms.txt](https://docs.podtorrent.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podtorrent.com/running-a-node/troubleshooting.md).

# Troubleshooting

## Agent log messages

| Message                                          | Cause                                                                | Fix                                               |
| ------------------------------------------------ | -------------------------------------------------------------------- | ------------------------------------------------- |
| `PODTORRENT_NODE_TOKEN is not set`               | No token                                                             | Set the environment variable                      |
| `engine at ... not reachable`                    | Engine isn't listening at `-engine`, or the container can't reach it | Check the URL and Docker network                  |
| `engine ... does not list these manifest models` | Model ids don't match                                                | Make `models[].id` match `/v1/models` exactly     |
| `link down, reconnecting ... 401`                | Wrong or revoked node token                                          | Check the token, or ask the team for a new one    |
| `link down, reconnecting ... dial`               | Can't reach the network                                              | Check the firewall and any proxy for outbound 443 |
| `request failed ... engine unreachable`          | Engine stopped or restarted mid-request                              | Check your engine's health                        |

## Common questions

**The agent is connected but I get no requests.** Clients may not be asking for your model, or other nodes may be cheaper or less busy. Compare your price with the [network offers](/using-the-api/models-and-offers.md#network-offers). Also check your `tiers` setting.

**My work shows as not paid.** Run agent v0.2.0 or newer, and make sure your engine returns `usage` in the last stream chunk. See [Receipts and billing](/concepts/receipts-and-billing.md).

**Inbound node never connects.** Check the agent is listening on the address you gave the team, the token is right (a `401` in the logs), and the tunnel or firewall lets the network through. The network retries every minute.

**I edited the manifest and nothing changed.** Look for an "invalid" message in the logs. The agent keeps the old manifest when the new one is broken, or when the engine doesn't serve a listed model.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.podtorrent.com/running-a-node/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.