Skip to content

Documentation v1.3.1

Configure a USB Proxy

Route HTTP or SOCKS5 proxy traffic through a supported USB device connected to the Localtonet client host.

Prerequisites

  • A Localtonet account and the Localtonet client installed and running on the host connected to the USB device.
  • A connected, device-specific AuthToken for that host.
  • The exact device model listed on My USB Devices. If it is not listed, contact Localtonet support instead of selecting another model.
  • The host detects the device, and the device has working internet access.
  • The device network does not overlap the host LAN, VPN, virtual networks, or another USB device.

For ADB-connected Android devices

Install ADB, enable USB debugging, connect with a data-capable cable, and authorize only the trusted host. Confirm the device and copy its reported identifier:

adb devices
  • device: recognized and authorized.
  • unauthorized: verify and approve the authorization prompt on the phone.
  • offline: reconnect the cable, unlock the phone, and restart the ADB relationship using the platform's normal tools.
  • No entry: check the cable, USB mode, driver, host permissions, and USB debugging.

Keep secrets private: Do not expose the AuthToken, proxy credentials, endpoint secrets, device identifier, or account details in commands, screenshots, logs, or support posts.

Configure and start the proxy

  1. Open My USB Devices. Enter a recognizable name, select the exact model, and save it. For an ADB device, enter the identifier reported by adb devices.
  2. Open My Tokens. Locate the device-specific token used by the client on this host, apply the current USB-device setting, and confirm that the token is connected.
  3. Open the Proxy Server page. Select the prepared AuthToken, choose HTTP or SOCKS5 as supported by the consuming application, select the USB device, choose an available relay server or region, and create the configuration.
  4. Use the Start control and wait until the proxy status shows that it is running or connected. Creating the configuration does not start it.
  5. Copy the assigned public host, port, and authentication values from the authenticated dashboard into the authorized proxy consumer.

Verify the exit device

  1. Record the consumer application's public IP without the proxy.
  2. Configure only that application to use the assigned proxy endpoint.
  3. Check its public IP again with a reputable external IP-check service. The result should correspond to the selected USB device's upstream connection.
  4. Test several normal requests to confirm stable connectivity.

For an HTTP proxy with curl:

curl --proxy http://PROXY_HOST:PROXY_PORT https://example.com/

For SOCKS5 with hostname resolution through the proxy:

curl --proxy socks5h://PROXY_HOST:PROXY_PORT https://example.com/

Use the authentication mechanism required by the created configuration without placing real credentials in shell history, shared scripts, process listings, or CI logs.

Troubleshooting

  • Device missing from the host: Use a data-capable cable, connect directly instead of through an unpowered hub, confirm the required USB mode, and check drivers and permissions.
  • Device missing from Localtonet: Confirm the exact model is supported, the saved ADB identifier matches adb devices, the token is configured for USB use, and the client using that token is connected on the same host.
  • Created proxy is unavailable: Confirm it was explicitly started, the selected token is connected, the client remains running, and the USB device is still connected and online.
  • Wrong exit IP or multiple devices fail together: Confirm the selected device and inspect the host routing table for overlapping USB, LAN, Wi-Fi, or VPN subnets. Common tools are route print on Windows, ip route on Linux, and netstat -rn on macOS.
  • Proxy fails after a reboot: Confirm the client is running with the intended token, the USB driver loaded, the device is reachable, and the proxy is started.
support