How to Use LocalProxies

1. Getting Connected

Whitelist your IP address

LocalProxies authenticates via IP whitelisting — no username or password is needed in your proxy client. After purchasing a plan, log in to your dashboard at amember.localproxies.com and navigate to the Proxy Ports page.

Under Allowed IPs, you will see a text area where you can paste one IP address per line. You can also click Add current IP to whitelist the IP you are browsing from right now. Click Update to save.

The number of IPs you can whitelist depends on your plan — 1 to 10 auth IPs depending on the tier. See pricing for details.

Your proxy endpoint

Each port on your account maps to a proxy endpoint:

Your endpoint is gate.localproxies.com:PORT, where PORT is the port number shown on your Proxy Ports page (e.g., 10001). Each port has its own configuration — country, rotation period, thread limit — that you can change at any time.

Both HTTPS and SOCKS5 protocols are available on every port. Most HTTP clients default to HTTPS. If your application needs SOCKS5, configure it explicitly (examples below).

2. Your First Request

Once your IP is whitelisted, test the connection. The simplest way is a curl command. No credentials are needed — just the proxy address.

Point your HTTP client at your proxy endpoint (e.g., gate.localproxies.com:10001) and make a request. The response will show the residential IP address assigned to your port. It should differ from your real IP. If you see your own IP, your whitelist entry may not have propagated yet — wait 30 seconds and retry. Both HTTPS and SOCKS5 protocols work on the same endpoint.

No credentials are required in the proxy URL. Authentication happens at the network level through your whitelisted IP. If your code runs on a server, whitelist the server's public IP in your dashboard.

curl --proxy http://gate.localproxies.com:10001 http://www.localproxies.com/show_ip.php

3. Configuring Geo-Targeting

Each port can be configured to route traffic through a specific country or region. Set this in the Port Options section on your Proxy Ports page.

Country targeting

The Country dropdown lists all available countries by ISO 3166-1 alpha-2 code. Select a country to restrict that port's traffic to residential IPs in that country. Set to Any to use the full global pool.

Country changes take effect on that port after a short propagation delay — no code changes are needed on your side.

Region targeting

Within a country, you can narrow to a specific region (US state, Canadian province, German Land, etc.) using the Region dropdown in Port Options. Available regions are listed in the dropdown for each country on the dashboard.

If no residential IPs are currently available in your targeted location, the proxy will connect you to the nearest available location within the same country. Browse all available locations on the locations page.

4. Session Management

LocalProxies offers two plan types that handle IP assignment differently. Understanding which to use is critical for your workflow.

Sticky sessions (ports)

On a sticky session plan, each port is assigned a residential IP that persists for at least 10 minutes. All devices connecting through the same port share the same proxy IP for the duration of the rotation period. This is ideal for:

• Multi-step workflows (login, navigate, extract)
• Paginated browsing where session continuity matters
• Account management tasks that require a consistent IP

The IP rotation period is configurable in Port Options. Set it in seconds — for example, 600 for 10 minutes, 1800 for 30 minutes. The system automatically assigns a new residential IP when the period expires. Many IPs naturally persist for several hours, but the 10-minute minimum is guaranteed.

You can also trigger a manual IP change at any time from the Proxy Ports page or via the API.

High rotation (threads)

On a high rotation plan, every new TCP connection gets a fresh IP from a different subnet. There is no session persistence — each request is independently routed. This is ideal for:

• Large-scale data collection across many URLs
• Price monitoring where you need maximum IP diversity
• Any workflow where IP uniqueness matters more than continuity

The plan's thread count is the maximum number of concurrent TCP connections you can have open at once. If your plan allows 40 threads and all 40 are in use, you must close one before opening another.

Choosing the right mode

5. Using with Common Tools

LocalProxies works with any proxy-aware tool or library. Point your HTTP client at gate.localproxies.com:PORT using standard HTTPS or SOCKS5 proxy settings. No credentials are required in the proxy URL — authentication is handled via IP whitelisting.

Compatible with curl, Python requests, Node.js (axios, undici), and any other HTTP client that supports proxy configuration. For SOCKS5, use the SOCKS5 connection method of your chosen library with the same endpoint.

Python (requests)

import requests
proxies = {"https": "http://gate.localproxies.com:10001"}
r = requests.get("https://example.com", proxies=proxies)
print(r.status_code, r.text[:200])

Node.js (undici)

import { fetch, ProxyAgent } from 'undici'
const agent = new ProxyAgent('http://gate.localproxies.com:10001')
const r = await fetch('https://example.com', { dispatcher: agent })

Browser / system proxy settings

You can configure your OS or browser to route all traffic through LocalProxies by setting the system proxy to gate.localproxies.com:PORT. Keep in mind that modern browsers can open 20-30 concurrent connections per tab, which counts against your thread limit. See the FAQ for more detail on thread usage with browsers.

6. API Endpoints

Two API endpoints are available from your Proxy Ports page. Both use simple HTTP GET or POST requests — no SDK required.

IP whitelist API

Add an IP address to your authorized list programmatically. Your unique token and user ID are displayed on the Proxy Ports page under the Allowed IPs section.

Send a GET or POST request to the whitelist endpoint shown on your Proxy Ports page, passing your token, user ID, and the IP address to whitelist. This is useful for dynamic environments (cloud functions, CI/CD pipelines) where your outbound IP changes frequently. Call this endpoint at the start of your workflow to whitelist the current machine before making proxy requests.

Manual IP change API

For sticky session ports, you can force an immediate IP rotation by calling the change IP URL displayed on your Proxy Ports page. After calling it, wait 5 seconds for the new IP to take effect. The full URL, including your secret token and port ID, is shown in your dashboard.

Rate limit: Manual IP changes are limited to a few times per hour per port. If you call it too frequently, you will receive a message asking you to retry in a few seconds.

Tip: You do not need to call the change IP API on high rotation plans. Those plans automatically assign a fresh IP for every new TCP connection.

7. Troubleshooting