The essential points from this guide -- each one is explained in detail below.
A residential proxy needs three things to work: a gateway address, a port, and login credentials from your provider.
Browsers, code libraries, and no-code tools all accept the same host, port, and username/password format.
Most connection failures trace back to a wrong credential format or an outdated IP allowlist entry, not a broken proxy.
Sticky sessions hold one IP for logins and checkout flows; rotating IPs suit large-scale scraping.
Store proxy credentials in environment variables or a secrets manager, never directly inside a script you might share.
Before you configure anything, gather three items from your proxy provider: a gateway hostname, a port number, and login credentials. KnoxProxy issues all three the moment you activate a residential proxy plan, priced at $2.10 per GB with access to IP addresses across 195+ countries.
Decide how you plan to connect first. A browser needs the host and port entered into network or extension settings. A Python or Node.js scraper needs the same values passed as proxy parameters in your request library. A no-code automation tool usually has a dedicated proxy field in its settings panel. Read our primer on what a residential proxy is if you have not already, so you know what real IP diversity buys you before you configure it.
Many people search for how to make residential proxies when what they actually want is a working connection they can use right away, not a from-scratch network build. Building a residential proxy network from real household devices requires opt-in software, device agreements, and infrastructure most businesses do not want to run themselves. Buying access through a provider like KnoxProxy skips that step entirely, since you get an active connection in minutes instead of building one.
Check your target use case against your budget before choosing a plan. Casual browsing or account management needs far less data than continuous web scraping. If you expect to pull thousands of pages a day, compare current pricing against your expected GB usage first, so you do not run out of data mid-task.
Follow these steps to set up a residential proxy in nearly any browser, script, or tool:
1. Copy your gateway address and port from your provider dashboard, for example gw.knoxproxy.com:8000. 2. Copy your username and password, or add your current IP to the provider's allowlist if you prefer IP-based authentication. 3. Open your target application's proxy settings. In a browser, this means system network settings or a proxy extension. In code, this means a proxy parameter in your HTTP client. 4. Enter the host and port in the address and port fields. 5. Enter your username and password, or confirm your IP is allowlisted. 6. Save the settings and send a test request.
If your task requires IPs from a specific country, such as United States residential IPs, select that location in your dashboard before copying the gateway address, since some gateways are location-specific.
For a Python scraper using the requests library, how to set up residential proxy access looks like this:
import requests
proxies = {
"http": "http://USER:PASS@gw.knoxproxy.com:8000",
"https": "http://USER:PASS@gw.knoxproxy.com:8000",
}
response = requests.get("https://api.ipify.org", proxies=proxies)
print(response.text)If the printed IP matches your proxy dashboard's assigned address instead of your real IP, the setup worked. If it still shows your real IP, check that the proxy parameter is actually being passed to the request and that no earlier code path bypasses it.
A 407 Proxy Authentication Required error almost always means your credentials did not reach the proxy, not that the proxy itself is broken. Check that your username and password are entered in the exact field the provider expects. Some browsers and libraries require the format username:password@host:port, while others have separate fields for each value.
If you use IP allowlisting instead of a username and password, confirm the IP address you added is your current one. Home internet connections and many VPNs change your public IP periodically, and an outdated allowlist entry will reject every request with the same 407 error even though the account itself is active and paid.
Special characters in a password, especially @, :, or /, can break a proxy URL string if they are not URL-encoded. Replace @ with %40 and : with %3A before dropping the password into a combined host string, or use your client library's dedicated username and password fields instead of building the URL by hand.
A dedicated username and password per project also helps you isolate which script or team member caused a failure, instead of guessing across a shared credential set. If authentication keeps failing after checking format and allowlist status, contact your provider's support team with the exact error message and gateway address rather than resending the same request repeatedly.
Sticky sessions and rotating IPs solve different problems, and using the wrong one causes most integration bugs. A sticky session keeps the same residential IP assigned to your connection for a set duration, commonly 1 to 30 minutes, so a website sees one consistent visitor across multiple steps.
Use sticky sessions for any flow the target site expects a single visitor to complete: logging in, adding items to a cart, or paginating through search results tied to one session. If the IP changes mid-flow, some sites will log you out or reset your session state, breaking the task.
Rotating IPs assign a new residential address on every request or after a short interval. This suits large-scale, independent tasks like scraping thousands of product pages or checking price listings across many URLs, where each request stands alone and a fresh IP avoids rate limits triggered by repeated requests from one address.
Most residential proxy plans, including KnoxProxy's, let you choose sticky or rotating mode per request by changing a parameter in your gateway connection string, rather than provisioning separate proxies for each mode. If you are still comparing providers, our best residential proxies roundup breaks down which services support both modes well.
A common mistake is leaving rotation on for a login flow, which logs the account out mid-session, or leaving a sticky session on for bulk scraping, which slows the whole job down to one IP's rate limit. Match the mode to the task before you start, not after you see failures.
Treat residential proxy credentials the same way you treat database passwords: never write them directly into a script you might share, commit to a repository, or paste into a public forum. Store the username and password in environment variables or a secrets manager, and load them into your code at runtime instead.
If your team shares one proxy account across multiple scripts or people, request separate sub-user credentials for each project instead of reusing a single login everywhere. This way, if one script leaks a password or misbehaves, you can revoke that one set of credentials without resetting access for every other project.
Rotate your password periodically, especially after any script, laptop, or shared document containing it changes hands. Most provider dashboards let you regenerate a password instantly, which immediately invalidates the old one across every connection using it.
Watch your usage dashboard for GB consumption that does not match your own activity. An unexpected spike often means a leaked credential is being used by someone else, not a billing error. If you are comparing options through our cheap residential proxies guide, check that per-user credentials are included at every price tier, since login isolation should not be a premium-only feature.
Finally, avoid IP allowlisting on shared or dynamic connections you do not control, since an allowlist tied to a public Wi-Fi IP can grant access to anyone else on that same network.
Ready to put this into practice? Browse Residential Proxies
KnoxProxy Research Team · Technical Content
Network engineers and proxy infrastructure specialists with 10+ years in anti-bot systems, web scraping, and IP routing.
90.4M+ ethically sourced residential IPs across 195 countries. Instant activation, 14-day money-back guarantee.