ProxyHubb Docs

Provider CLI

Install provider-node, download config, start the tunnel — do not re-register after the wizard.

Provider CLI

Providers sell bandwidth by running provider-node (tunnel daemon) against proxy.proxyhubb.com:3128.

Recommended path

  1. Complete the in-app provider setup wizard
  2. Download CLI + provider.toml from CLI Tools
  3. Start the node — do not run register again after the wizard

Downloads

Binaries ship via GitHub Releases and GET /v1/cli/download (platform/arch). The dashboard detects your OS and offers the matching asset.

Config

Typical config includes control-api URL, provider token, tunnel endpoint, and provider_signing_key for usage proofs. Keep provider.toml private.

Start

# example — exact binary name varies by release
./provider-node --config provider.toml
# or service/install helpers from the release bundle

Confirm the node goes online under My nodes. Browser “ping” is not a real tunnel — use Connect + CLI start.

Proof signing

If the dashboard shows unsigned usage / “Fix proof”, ensure provider_signing_key in the CLI config matches the key bound at registration (CLI register generates it; web-only flows may need the fix banner path).