Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs(node): tell operators about the resolved-address policy
Peer and webhook hostnames must now resolve to public addresses, the node
ignores proxy environment variables for that traffic, and the operator's
Kubo endpoint is unaffected.
  • Loading branch information
beardthelion committed Nov 18, 2026
commit b0e572f3575820c664de9cd19319b17c40f07843
2 changes: 2 additions & 0 deletions docs/RUN-A-NODE.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,8 @@ Optional:
- `TWIGPINE_HEARTBEAT_INTERVAL_HOURS=20` — how often to post heartbeats (must be < 24)
- `TWIGPINE_RECONCILIATION_SWEEP=true` — enable the hourly durability sweep that re-pins/backstops missing objects (default `true`; disabled when no IPFS/Pinata backend is configured). Public pin repair runs against any configured backend. Encrypted recovery repair requires local IPFS (`TWIGPINE_IPFS_API`); Pinata-only nodes reconcile public pins only. Set `=false` to disable.

Outbound requests to URLs other people choose (peer announce and ping, bootstrap, webhook delivery, and the sync worker's git fetch of a peer) resolve each hostname and connect only when every resolved address is public. A peer or webhook hostname that resolves to a loopback, private, link-local or cloud-metadata address is refused and logged once at `warn`. The node ignores `HTTP_PROXY`, `HTTPS_PROXY` and `ALL_PROXY` for that traffic. `TWIGPINE_IPFS_API` is unaffected: it is your own endpoint and keeps working on a private or loopback hostname.

## 5. Verify

```bash
Expand Down