> 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/connection-modes/cloudflare-tunnel.md).

# Cloudflare Tunnel

Use this when you want no public endpoint and no inbound ports. Your `cloudflared` makes outbound connections only, and the network reaches your agent through it.

## Steps

1. **Ask the PodTorrent team for a tunnel.** They create one for your node and send you a tunnel token and a hostname such as `node-01.tunnel.podtorrent.com`. The hostname is locked down so only the network can reach it.
2. **Run the agent in inbound mode** on a local address. Plain HTTP is fine here because the tunnel encrypts the traffic:

   ```bash
   podtorrent-agent -listen 127.0.0.1:8443 -insecure-plaintext \
     -engine http://127.0.0.1:8000 -manifest manifest.json
   ```
3. **Run `cloudflared`** next to it:

   ```bash
   cloudflared tunnel run --token <tunnel token> --url http://127.0.0.1:8443
   ```
4. **Tell the team it's running.** They register the link, and the network connects within a minute.

{% hint style="warning" %}
Only use `-insecure-plaintext` on a local address behind the tunnel, never on an address other machines can reach.
{% 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 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/connection-modes/cloudflare-tunnel.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.