CLOAKBROWSER + PROXIES.SX

1. CHOOSE THE ROUTE FIRST

Open Pool Proxy, choose your country and network, then copy the generated username. Check live stock before testing. If that selection has no stock, stop and choose another route explicitly; do not remove the country or carrier filter to make an error disappear.

Use the separate proxy password from your account, not your login password or API key. For a browsing workflow, choose sticky rotation and one session ID per browser. Sticky holds a device while eligible and connected; it does not guarantee an unchanged public IP. Keep passwords out of source code, screenshots and shared logs.

2. INSTALL AND RUN

This example uses Node.js 22.12 or newer, cloakbrowser@0.6.2 and playwright-core@1.64.0. CloakBrowser downloads its browser on first launch. See its installation instructions for platform support and browser versions; a wrapper version is not a Chromium version.

mkdir proxies-cloak-test
cd proxies-cloak-test
npm init -y
npm install --save-exact cloakbrowser@0.6.2 playwright-core@1.64.0

Set PROXIES_SX_USERNAME and PROXIES_SX_PASSWORD in your local environment or secret manager. Copy the complete generated username, including its filters and session ID. Save this as proxies-cloak.mjs, then run node proxies-cloak.mjs.

import { launch } from 'cloakbrowser';

const username = process.env.PROXIES_SX_USERNAME;
const password = process.env.PROXIES_SX_PASSWORD;
if (!username || !password) {
  throw new Error('Set PROXIES_SX_USERNAME and PROXIES_SX_PASSWORD first.');
}

const browser = await launch({
  headless: true,
  proxy: {
    server: 'http://gw.proxies.sx:7000',
    username,
    password,
  },
});

try {
  const page = await browser.newPage();
  const response = await page.goto('https://example.com/', {
    waitUntil: 'domcontentloaded',
    timeout: 30000,
  });
  if (!response?.ok()) {
    throw new Error(`Target returned HTTP ${response?.status() ?? 'unknown'}`);
  }
  console.log({ status: response.status(), title: await page.title() });
} finally {
  await browser.close();
}

The browser uses the HTTP gateway on port 7000 to tunnel the HTTPS target. Keeping authentication in separate fields avoids mistakes with special characters in passwords. This guide tests that HTTP configuration; it does not claim authenticated SOCKS5 compatibility for every CloakBrowser binary.

3. UNDERSTAND THE RESULT

A 200 response and the expected title establish that this navigation worked. Then test the page and permitted workflow you actually need at low concurrency. A working example page is not proof that every target accepts the exit, that geolocation databases agree, or that a long session will keep its IP.

Usage is metered. Check the selected country's current rate in the portal or the stock API's pricing block; browser subresources and retries also transfer bytes. Browser licensing is separate from proxy bandwidth.

WHAT WE VERIFIED

On 14 October 2026, we installed the two exact npm versions above in a clean project and launched CloakBrowser's downloaded, signature-verified macOS ARM64 Chromium 145.0.7632.109.2. A controlled HTTP proxy challenged for authentication and served the expected page through the browser. The test used fixture credentials, included special characters in the password, and made no customer-account traffic.

This verifies browser launch and proxy configuration, not production availability or target access. The HTTPS example should still be tested against your own account and currently available route. No reciprocal listing or endorsement by CloakBrowser is implied.

MORE

Gateway contract and errors · AI-readable integration instructions · All integration guides · CloakBrowser