Skip to content

Documentation v1.3.1

Configure a USB Proxy

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

Prerequisites

  • A Localtonet account and a running Localtonet client on the host that can communicate with the USB device.
  • A connected, device-specific AuthToken.
  • A device whose exact model appears on My USB Devices.
  • Required model-specific drivers or USB networking mode, plus working internet access through the device.
  • A device subnet that does not overlap the host LAN, VPN, virtual networks, or another USB device.

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

Configure the proxy

  1. Confirm host access. Check that the operating system detects the device without driver, authorization, or permission errors. Use a data-capable USB cable.
  2. For an ADB device, confirm authorization. Enable USB debugging on a device you control, approve only the trusted host, and run:
    adb devices
    The result must show device. Use the displayed ADB identifier when registering the device.
  3. Register the device. Open My USB Devices, enter a recognizable name, select the exact model, and provide the ADB identifier when applicable. If the model is absent, use the Localtonet support form instead of selecting a substitute.
  4. Configure the token. Open My Tokens, select the device-specific token used by the client on this host, apply the current USB-device setting, and confirm that the token is connected.
  5. Create the proxy. Open the Proxy Server page. Select the prepared AuthToken, HTTP or SOCKS5 according to consumer support, the intended USB device, and an available relay server or region. Create the configuration.
  6. Start the proxy. Select Start and wait until its status shows that it is running or connected. Creating a proxy does not start it.
  7. Configure the consumer. Copy the assigned public host, port, and authentication values from the authenticated dashboard into the corresponding proxy fields.

Verify the exit

Compare the consumer application's public IP without the proxy and with the proxy enabled. The proxied IP should correspond to the selected USB device's upstream connection.

For an HTTP proxy with curl:

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

For SOCKS5 with proxy-side hostname resolution:

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

Use the authentication mechanism assigned to the proxy without placing real credentials in shell history, shared scripts, process listings, or logs.

Troubleshooting

  • ADB shows unauthorized: Unlock the phone, verify the authorization prompt belongs to the trusted host, and approve it.
  • ADB shows no entry: Check the cable, USB mode, driver, host permissions, and USB debugging setting.
  • Device is absent from Localtonet: Confirm the exact model, compare the registered identifier with adb devices, verify the token is configured for USB use, and confirm the client 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 still has internet access.
  • Multiple devices fail together: Inspect the host routing table for duplicate or overlapping private subnets. Distinct gateway addresses within the same subnet do not create separate networks.
  • Unexpected exit IP: Confirm the selected USB device, stop other test proxies, check for overlapping USB, LAN, Wi-Fi, or VPN routes, and ensure the application did not fall back to a direct connection.
support