All setup guides

Proxies in
Node.js (fetch / undici).

HTTPNode.js

Get your connection details

Open your Residential, Datacenter, ISP or IPv4 access in the dashboard, then its configuration tab. Select the protocol shown here, your country and session settings.

Static ISP
Dedicated residential ISP IP with unlimited bandwidth — from $1.90 / ≈ $1.94 per IP (from 7 days). Best for accounts, profiles and messengers.
Rotating Residential
183 countries, cities and ASNs, rotating or sticky up to 30 min — from $0.60 / ≈ $0.60 per GB. Traffic never expires.
Rotating Datacenter
65 countries, up to 1 Gbps speed, sticky up to 24 h — from $0.40 / ≈ $0.40 per GB. Built for scraping and automation.
Dedicated IPv4
Dedicated datacenter IPv4 with one tenant and unlimited bandwidth — from $1.40 / ≈ $1.44 per IP.
host
Server address
port
Port for this protocol
login
Proxy username
password
Proxy password

Copy the fields separately. Proxy credentials are different from your Proxly account login. After changing the location, copy the updated proxy username again.

Open your connection

Connect the app

  1. Install undici for built-in fetch: npm install undici.

  2. Set the PROXLY_PROXY_URL environment variable (http://login:password@host:port) from your Proxly dashboard.

  3. Pass new ProxyAgent(process.env.PROXLY_PROXY_URL) in the dispatcher option of fetch and run the script.

Connection example
import { ProxyAgent } from "undici";

const agent = new ProxyAgent(process.env.PROXLY_PROXY_URL);
const res = await fetch("https://api.ipify.org?format=json", {
  dispatcher: agent,
});
console.log(await res.json());

In Node.js 18+, built-in fetch is powered by undici and accepts a ProxyAgent via the dispatcher option.

Test the connection

The console outputs { ip: '...' } with the proxy IP address.

Turn the proxy off

Remove the dispatcher property from the fetch options.

If the connection fails

Authentication error

Recopy the proxy credentials. Include the full username with location and session settings. HTTP status 407 means proxy authentication was not accepted.

Connection timeout

Check the dashboard host and the port for the selected protocol. Make sure the access has remaining data. Use HTTP for Chromium with username and password.

The IP did not change

Check the IP inside the configured app or browser profile. Make sure the test site is not excluded from the proxy. Telegram does not change your regular browser IP.

Still having trouble? Contact support

App documentation:Node.js Undici