This guide gets you from zero to a working Residential proxy connection.
Looking for a different product? See Getting Started with Mobile proxies or Getting started with ISP proxies.
Your connection details
Setting | Value |
Host | gate.nodemaven.com |
HTTP / HTTPS ports | 8080-9080 and 32000-33000 |
SOCKS5 ports | 1080-2080 and 42000-43000 |
Username | Your proxy username, plus any targeting parameters |
Password | Your proxy password |
Any port within those ranges works. The dashboard gives you 8080 for HTTP and 1080 for SOCKS5 by default, but if a port is blocked on your network, just pick another one from the range.
Step 1 - Get your credentials
Go to Rotating Residential Proxy in the dashboard and make sure Connection type is set to Residential. Your Proxy username and Proxy password appear under Proxy generator.
Step 2 - Check your proxy works
Before setting anything up elsewhere, confirm the proxy is healthy. Click Check proxy next to your generated proxy in the dashboard.
We run a live check and show you three things:
Fraud risk - for example, "Low fraud risk."
Resolved location and IP - for example, "US, New York, New York City, 188.215.124.227"
A link to Scamalytics for that IP, if you want the full report
This takes one click, needs nothing installed, and confirms both that the proxy works and that it is coming out where you expect. Do this first whenever something looks wrong.
Step 3 - Make your first request from your own tools
Once Check proxy looks good, you can wire the proxy into your own code. Replace USERNAME and PASSWORD with your own credentials in one of the examples below.
Keep the quotes. In all three examples the credentials sit inside quote marks. Replace only the USERNAME and PASSWORD text, leave the quotes in place.
curl -x "http://USERNAME-country-us:[email protected]:8080" https://ipinfo.io/json
Python
import requests
username = "USERNAME-country-us"
password = "PASSWORD"
proxy = f"http://{username}:{password}@gate.nodemaven.com:8080"
response = requests.get(
"https://ipinfo.io/json",
proxies={"http": proxy, "https": proxy},
)
print(response.text)
Node.js
const axios = require('axios');
const { HttpsProxyAgent } = require('https-proxy-agent');
const agent = new HttpsProxyAgent(
'http://USERNAME-country-us:[email protected]:8080'
);
axios.get('https://ipinfo.io/json', { httpsAgent: agent })
.then(res => console.log(res.data));
Python and Node examples will not work if you paste them straight into a terminal. They are programs, not shell commands - save them to a file first and run the file. Only the cURL example runs directly in a terminal.
If the response shows a US IP rather than your own, your proxy is working.
Step 4 - Target a location
Residential proxies cover 205 countries with region, city, ISP, and ZIP targeting. Add parameters to your username as key-value pairs:
USERNAME-country-us-region-california-city-los_angeles
Parameter | Example | What it does |
|
| Country, two-letter code |
|
| State or province |
|
| City |
|
| ZIP or postal code (replaces region and city) |
Easier option: set the location in the dashboard and copy the generated username. Country and Region show a High badge where we have strong inventory.
For the full list, see Available locations.
Step 5 - Session control
Under Advanced settings, pick a Session type:
Sticky (default) - holds the same IP for up to 24 hours. If that IP goes offline you get a new one from the same location, so your connection keeps working.
No rotating - the IP never changes, even if it goes offline. The session waits for your original IP to return rather than substituting another. Use this when a different IP would break your workflow. To get a new IP, generate a new proxy string with a new SID or change the SID in your current proxy string.
Rotating - a new IP on every request. Best for scraping and price monitoring.
In the username:
Sticky USERNAME-country-us-sid-abc123
No rotating USERNAME-country-us-sid-abc123-norotate-true
Rotating USERNAME-country-us
Sticky also takes a Custom duration in seconds, from 60 seconds up to 86,400 seconds. This appears as -ttl- in the username, so 500 seconds becomes -ttl-8m20s.
Step 6 - Choose an IP filter mode
Also under Advanced settings, IP filter mode controls which IPs you route through:
Mode | Username parameter | Use when |
Quality (default) |
| You want the cleanest IPs and best success rate |
Quality + Speed |
| Clean IPs but also low latency |
Speed |
| Latency matters more than filtering |
Max pool size | (none) | Maximum IP variety, typically for scraping |
Quality suits most work. Change it only if you have a specific reason.
Step 7 - Copy your proxy string
The Proxy generator builds your full string as you change settings. Two formats are available: Host:Port, which most anti-detect browsers and proxy tools expect, and Protocol, for code and command-line tools.
Set Proxies quantity to generate several at once, then copy them or Export as .csv or .txt.
Step 8 - Use it in your tool
Scroll to Open in Anti-detect browser to launch straight into a supported tool: Dolphin{anty}, BitBrowser, AdsPower, MostLogin, GeeLark, DICloak.
For step-by-step setup in these and other tools, see the Integrations section of this help center.
Tracking your usage
Go to Dashboard in the left navigation for traffic and request charts, plus a breakdown by domain showing exactly which sites your traffic went to. Filter by user, product, and time period.
If something isn't working
Check your username and password are copied exactly, with no trailing spaces
Confirm your port is inside the supported ranges - 8080-9080 or 32000-33000 for HTTP, 1080-2080 or 42000-43000 for SOCKS5
If one port is blocked on your network, try another from the range
Use Check proxy to confirm the IP itself is healthy
If the location looks wrong in an anti-detect browser, check that browser profile's own timezone and geolocation settings - those override what the proxy reports
For more, see the Troubleshooting section of this help center.