Mobile Proxy Node.js Setup

Node.js Proxy Options

Unlike browser runtimes or Python, Node.js does not automatically read HTTP_PROXY environment variables out of the box for built-in HTTP requests. In modern JavaScript and TypeScript backends, routing outbound traffic through a proxy requires configuring an Agent dispatcher or passing network parameters into high-level browser automation frameworks.

axios and node-fetch Setup

When using axios, developers frequently attempt to pass a basic { host, port, auth } proxy object. While this works for plaintext HTTP, it often causes connection reset errors on HTTPS targets. The industry standard solution is to install https-proxy-agent or socks-proxy-agent to establish clean HTTP CONNECT tunnels.

import axios from 'axios';
import { HttpsProxyAgent } from 'https-proxy-agent';

// Define dedicated PXM2 mobile proxy endpoint
const proxyUrl = 'http://user123:secret456@proxy.pxm2.io:8000';
const httpsAgent = new HttpsProxyAgent(proxyUrl);

// Create reusable axios client instance
const client = axios.create({
  httpsAgent,
  timeout: 15000,
  headers: {
    'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36',
  },
});

async function checkCarrierIp() {
  try {
    const response = await client.get('https://ipinfo.io/json');
    console.log('Connected through mobile IP:', response.data.ip);
  } catch (err) {
    console.error('Proxy request failed:', err.message);
  }
}

checkCarrierIp();

For SOCKS5 proxies in Node.js, install socks-proxy-agent and initialize SocksProxyAgent('socks5h://user:pass@proxy.pxm2.io:1080'). The socks5h protocol ensures remote DNS resolution without client-side leaks.

Puppeteer Proxy Configuration

Puppeteer launches an external Chromium binary. Because Chrome does not accept inline user and password credentials in its command line arguments, Puppeteer requires a two-step process: launching the browser with --proxy-server and calling page.authenticate() to supply credentials over the Chrome DevTools Protocol (CDP).

import puppeteer from 'puppeteer';

async function runBrowser() {
  const browser = await puppeteer.launch({
    headless: 'new',
    args: [
      // 1. Pass host and port to Chrome flags
      '--proxy-server=http://proxy.pxm2.io:8000',
      '--no-sandbox',
    ],
  });

  const page = await browser.newPage();

  // 2. Intercept 407 authentication challenges
  await page.authenticate({
    username: 'user123',
    password: 'secret456',
  });

  await page.goto('https://ipinfo.io', { waitUntil: 'domcontentloaded' });
  const ip = await page.$eval('body', el => el.innerText);
  console.log('Puppeteer IP verified:', ip);

  await browser.close();
}

runBrowser();

Playwright Proxy Setup

Playwright provides cleaner proxy ergonomics than Puppeteer. Instead of relying on CDP authentication interception, Playwright allows you to define proxy settings at the context level. This makes it possible to assign different mobile proxies to separate browser contexts concurrently inside a single Chromium instance.

import { chromium } from 'playwright';

async function main() {
  const browser = await chromium.launch({ headless: true });

  // Create isolated context with dedicated mobile proxy
  const context = await browser.newContext({
    proxy: {
      server: 'http://proxy.pxm2.io:8000',
      username: 'user123',
      password: 'secret456',
    },
    userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36',
  });

  const page = await context.newPage();
  await page.goto('https://api.ipify.org?format=json');
  console.log(await page.textContent('body'));

  await context.close();
  await browser.close();
}

main();

Node.js Proxy Best Practices

When running Node.js scrapers and bots at scale, proper connection pooling and memory hygiene are vital:

• 1. Enable Keep-Alive on Proxy Agents
  Always set keepAlive: true in your HttpsProxyAgent options. Reusing persistent TCP sockets saves 100ms–250ms of cellular latency on every sequential request.
• 2. Close Idle Contexts
  In Playwright and Puppeteer, never leave unused browser contexts or pages open. Lingering contexts consume memory and keep open socket connections to the cellular modem.
• 3. Handle On-Demand Rotation Delays
  When triggering an IP rotation via the PXM2 webhook in Node.js, wrap the rotation call in a Promise that pauses for 6 seconds before resolving your request queue.

Frequently Asked Questions

Related Mobile Proxy Guides

Explore related developer tutorials, language integrations, and mobile proxy infrastructure guides.

Developer Guides

Platform & Scraping Guides