Using Proxies with node-fetch and Undici
Practical Node.js proxy patterns for fetch/undici—HTTP agents, auth headers, retries, and Proxy Grove Unlimited endpoints from $2/IP/day.
Node fetch through a proxy usually means configuring an HTTP(S) agent or undici ProxyAgent with your Proxy Grove host, port, and credentials.
Proxy Grove Unlimited (live pricing): Residential/Corporate from $2/IP/day, Mobile from $4.50/IP/day; 1/7/30/90 days; HTTP+SOCKS5; sticky or rotating; fair-use unlimited traffic on the plan.
Production habits
Timeouts, retries with jitter, and per-request proxy labels in logs. Related: Axios, Puppeteer, Playwright.
Error handling
Treat 407 as auth misconfig, 502/504 as upstream or egress issues, and target 403 as policy—not always a “bad proxy.” Retry with jitter; do not stampede.
SOCKS note
If you need SOCKS5, confirm the endpoint protocol and use a SOCKS-aware agent. Product page: SOCKS5 proxies.
Buy on Proxy Grove
Open pricing or register at app.proxygrove.com. Pick residential, mobile, or corporate. Worldwide: 246 countries.
Solutions Engineer. Jordan helps teams design proxy architectures for scraping, monitoring, and secure outbound access.
Questions this article answers
In Node you typically attach a dispatcher/agent—check your runtime docs.
Use a SOCKS agent library and confirm endpoint protocol.
Pin one Proxy Grove endpoint label per session.
Unlimited from $2/IP/day on published plans.