How to Set Up a Proxy Server: Windows, Browsers, Bots

To set up a proxy server, you need five details from your provider: host, port, username, password, and protocol. On Windows 11, open Settings > Network & internet > Proxy, select Set up next to Use a proxy server, enter the host and port, and save. Bots, browsers, and scripts take the same details in their own proxy fields.

You normally do not need to build the proxy server yourself. The job is to route a browser, bot, scraper, or script through an endpoint that already exists, in the format that tool accepts. If you do want to run your own server, the section near the end covers a locked-down Squid install and a two-minute SSH tunnel. If you are not sure where your details are, what is a proxy address shows how to find them.

Start by testing one proxy in one client before loading a full list into automation. If the proxy works in cURL or a browser but fails in your bot, the issue is usually format, protocol, authentication, session handling, or request pacing rather than the proxy itself.

For most web workflows, use HTTP(S) proxies unless the tool explicitly asks for SOCKS5. If you are still choosing protocol, read SOCKS5 vs HTTP proxy. If you need rotating consumer-style traffic, start with residential proxies. If you need stable dedicated IPs for accounts, monitoring, or retail automation, compare ISP proxy plans.

How to set up a proxy server: quick steps

Use this setup flow for almost any proxy-backed workflow:

1. Copy the proxy host, port, username, password, and protocol from your dashboard.
2. Confirm whether the tool expects HTTP, HTTPS, SOCKS4, or SOCKS5.
3. Convert the proxy into the format the tool accepts.
4. Test one proxy with a simple IP-check endpoint.
5. Load a small batch into your browser, bot, or script.
6. Assign proxies consistently to accounts, sessions, or tasks.
7. Add delays, retries, and backoff before increasing concurrency.
8. Log failures with proxy, URL, status code, account, and timestamp.

Do not start by importing hundreds of proxies into a full task run. A small controlled test tells you whether the setup is valid before request volume, cookies, accounts, and anti-bot behavior make the results noisy.

Know your proxy details first

Most proxy setup problems come from mixing up fields.

You usually need:

Common formats include:

Format is not the same as protocol. A bot may ask for host:port:user:pass while still using an HTTP proxy under the hood. A script may require the http:// or socks5:// scheme to select the protocol. Use the proxy converter when you need to reformat a list without manually rearranging fields.

Set up a proxy in Windows and browsers

For normal browsing, there are three common options: the system proxy, a per-browser or per-profile proxy, or the proxy setting of an automation framework.

Use system proxy settings when supported browsers and apps should share a proxy. Some clients ignore these settings, so verify each application. The setting can also affect more traffic than intended.

Windows 11 system proxy

To set up a proxy server in Windows 11:

1. Open Settings > Network & internet > Proxy.
2. Under Manual proxy setup, select Set up next to Use a proxy server.
3. Turn on Use a proxy server.
4. Enter the proxy IP address or hostname and the port.
5. Add any addresses that should skip the proxy, separated by semicolons, then select Save.

Windows has no username or password field on this screen. Apps that use the system proxy ask for credentials when they first connect. If that prompt does not work in your tool, ask your provider to allowlist your public IP. This screen sets an HTTP-style web proxy only. It does not accept a SOCKS5 endpoint.

If your network gave you a script URL instead of a host and port, use Use setup script on the same page and paste the address there. That is a PAC file, and Microsoft's proxy settings article covers both modes. Older guides send you to Control Panel > Internet Options > Connections > LAN settings. Press Win + R and run inetcpl.cpl to open it. It edits the same per-user setting.

To turn the proxy off, switch off Use a proxy server and Use setup script on the Proxy page. Chrome and Edge follow this setting, so one change covers both. Firefox keeps its own proxy settings unless it is set to use the system proxy.

Other devices and browsers

The guides below cover each one in detail.

If Chrome shows ERR_PROXY_CONNECTION_FAILED, verify the system setting, extension or policy owner, and one proxy endpoint before clearing browser data or replacing a full list.

If the Windows troubleshooter reports that it could not automatically detect the network's proxy settings, check automatic, script, manual, and WinHTTP configuration separately before resetting the network.

On macOS, the Mac proxy settings guide covers the Network panel, HTTP and HTTPS fields, SOCKS endpoints, PAC files, browser behavior, verification, and safe removal.

Windows requires a separate method for SOCKS5 because its manual web proxy and WinHTTP settings are not a native SOCKS5 route. Use the Windows 11 SOCKS5 proxy guide for app-level setup, authenticated cURL testing, Chrome limitations, and multi-app routing.

Android needs an extra protocol check because its native Wi-Fi proxy field is not a SOCKS5 selector. Use the Android SOCKS5 proxy guide to choose between an app setting, a VPN-service-based client, and the built-in HTTP proxy fallback.

On iPhone, the built-in setting is also attached to one saved Wi-Fi network. Follow the iPhone HTTP proxy setup guide for manual credentials, PAC mode, route verification, and the limits around cellular data and app coverage.

Per-profile and automation proxies

Use a browser extension or browser profile when you need different proxies per profile, region, account, or test case. This is usually better for QA, local SEO checks, account workflows, and comparing locations without changing the whole device.

Firefox can configure an unauthenticated or source-IP-allowlisted SOCKS5 endpoint inside the browser profile. Follow the Firefox SOCKS5 proxy guide for the current and older Settings paths, proxy-side DNS, verification, and the manual form's username/password limitation.

For Chrome specifically, the Chrome SOCKS5 proxy setup guide compares extensions, launch flags, system routing, DNS behavior, and the browser's SOCKS5 authentication limitation.

Use browser automation settings when Playwright, Puppeteer, Selenium, or another automation framework launches the browser. In that case, configure the proxy in the automation tool rather than inside the browser UI. If an AI model drives the browser instead of a fixed script, the agentic browser guide explains where the proxy belongs for local, vendor-hosted, and self-run agents.

Test one proxy in the browser

For a manual browser test:

1. Choose one proxy endpoint.
2. Add the host and port to the browser, extension, or operating system proxy settings.
3. Enter username and password when prompted.
4. Visit an IP-check page.
5. Confirm the displayed IP and region match the proxy.
6. Open the target site only after the basic proxy test works.

If the browser repeatedly asks for credentials, check the username, password, and whether special characters need URL encoding. If pages load without the proxy IP changing, the browser may be bypassing the proxy because the system setting, extension scope, or profile setting is wrong.

Set up proxies in bots

Most retail bots, ticketing tools, monitoring tools, and automation apps accept proxy lists in one of these shapes:

host:port:username:password
username:password@host:port
http://username:password@host:port
socks5://username:password@host:port

Match the bot's import format exactly. If the bot has a protocol dropdown, do not also force a conflicting scheme in the proxy text. If it has separate fields for host, port, username, and password, paste each value into the matching field instead of using a full proxy URL.

For account, ticketing, or checkout workflows, map one account or profile to one stable proxy identity. That usually means ISP proxies or sticky residential sessions, not rotating on every request. The sticky vs rotating proxies guide explains when each session type fits. For product monitoring, repeated checks, or Refract-style retail workflows, stable task-to-proxy assignment is usually easier to debug than random reassignment on every loop.

For sneaker bots, the sneaker proxies guide compares ISP and residential setups for drops. If you are using Refract, the Refract Bot Target guide walks through proxy groups, task setup, and delay sizing for that specific bot. This article stays broader: the same setup discipline applies whether the bot is for retail monitoring, scraping, QA, or account operations.

Set up proxies in scripts

Scripts need explicit proxy configuration. Environment variables may work for some tools, but production jobs should make proxy behavior obvious in code or deployment config.

For cURL, test one HTTP proxy like this:

curl --proxy "http://username:password@host:port" https://ipv4.unknownproxies.com/ip

For SOCKS5:

curl --proxy "socks5://username:password@host:port" https://ipv4.unknownproxies.com/ip

For Python requests:

import requests

proxy = "http://username:password@host:port"
proxies = {
    "http": proxy,
    "https": proxy,
}

response = requests.get("https://ipv4.unknownproxies.com/ip", proxies=proxies, timeout=20)
print(response.text)

For more requests examples, including HTTPS targets, authentication, SOCKS5, and retries, read the Python proxy requests guide.

For Playwright:

import { chromium } from "playwright";

const browser = await chromium.launch({
  proxy: {
    server: "http://host:port",
    username: "username",
    password: "password",
  },
});

const page = await browser.newPage();
await page.goto("https://ipv4.unknownproxies.com/ip");
console.log(await page.textContent("body"));
await browser.close();

If your browser automation stack is Puppeteer, the Puppeteer use proxy guide explains when to use Chrome launch arguments, browser context proxy settings, or a fresh browser per proxy identity.

Keep secrets in environment variables or a secrets manager when the script runs outside a local test. Do not commit proxy passwords to the repo, paste them into issue trackers, or print full proxy URLs in application logs.

Choose residential, ISP, or datacenter proxies

Proxy setup is easier when the proxy type fits the workflow.

If you are deciding between proxy categories, read datacenter proxies vs residential proxies. If the decision is stable dedicated IPs versus rotating pool access, compare ISP proxies vs residential proxies.

Residential proxies are useful when rotation, location coverage, and consumer-style IP reputation matter. ISP proxies are useful when the same task, account, or browser profile should keep the same IP. Neither option fixes bad timing, broken cookies, account-level limits, or target rules.

Keep sessions consistent

A proxy setup that works for one request can still break a session.

Keep these values aligned inside a session:

• Proxy identity.
• Browser profile.
• Cookie jar.
• Login account.
• User agent.
• Region or locale.
• Task assignment.
• Retry and delay behavior.

If a login starts on one IP and continues on another, the site may treat that as a session risk. If a scraper rotates IPs but reuses cookies from a previous identity, it can create confusing behavior. Use sticky residential sessions or ISP proxies for multi-step flows. Use rotating residential sessions for independent requests where continuity does not matter.

For a deeper session design walkthrough, read how to use residential proxies.

Test before you scale

Use a simple test plan:

1. Test without a proxy to confirm the client works.
2. Test one proxy against an IP-check endpoint.
3. Test one proxy against the target homepage.
4. Test one proxy against the exact target endpoint.
5. Add authentication, cookies, and headers.
6. Add a small number of concurrent tasks.
7. Increase volume only after status codes and latency are stable.

Log the response status, response body snippet, proxy ID, target URL, and retry count. That data separates proxy setup errors from target-side rate limits, WAF blocks, application bugs, and account problems.

If the client only reports a vague failure, use the proxy error troubleshooting guide to classify configuration, authentication, connection, timeout, and target-response problems before changing the setup.

Troubleshooting proxy setup

Use the symptom to narrow the issue:

For repeated HTTP 429 Too Many Requests, slow down before adding more proxies. For HTTP 403 Forbidden, check whether authentication, authorization, target policy, or IP reputation is the real cause.

Production checklist

Before running a proxy-backed job in production, confirm:

• The proxy format matches the client.
• The protocol matches the provider and tool.
• Secrets are not committed or logged.
• Sessions are mapped to accounts or tasks consistently.
• Retry logic uses backoff instead of immediate loops.
• Timeouts are long enough for the proxy type.
• 403, 429, timeout, and CAPTCHA responses are tracked separately.
• The workflow follows site terms, robots guidance, and applicable law.
• Bandwidth-heavy pages are cached or trimmed when possible.

Use the delay calculator for monitoring-style workloads where proxy count, task count, and delay interact. A setup that looks fine at one request every few seconds can fail quickly when every worker retries at the same time.

Run your own proxy server

Sometimes you do want your own server, for example to give a few office machines one shared exit or to route a script through a VPS. There are two practical options. Squid is a full HTTP proxy that several clients can share. An SSH tunnel is a personal SOCKS proxy you can start in one command.

Option 1: Squid on Ubuntu or Debian

Squid is a common open-source choice. These steps are for Ubuntu or Debian.

1. Install Squid:

   sudo apt update
   sudo apt install squid
   

2. Open /etc/squid/squid.conf. Find the comment INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS and add your client IPs above http_access deny all:

   acl myclients src 203.0.113.10
   http_access allow myclients
   

3. Check the config and restart the service. Squid listens on port 3128 by default.

   sudo squid -k parse
   sudo systemctl restart squid
   

4. Open the port only to those clients at the firewall:

   sudo ufw allow from 203.0.113.10 to any port 3128 proto tcp
   

5. Test from the client machine:

   curl --proxy "http://SERVER_IP:3128" https://ipv4.unknownproxies.com/ip
   

Never add http_access allow all. That turns the server into an open proxy, and scanners look for those all the time. Our guide on what an open proxy is shows how to test for that and how to add username and password authentication to Squid.

Option 2: an SSH SOCKS tunnel

If you have SSH access to any server, you already have a proxy. Run this on your own machine:

ssh -D 1080 -N -C user@your-server.example.com

-D 1080 starts a local SOCKS server on port 1080 and forwards each connection over the SSH session. -N skips the remote shell, and -C compresses the traffic. The OpenSSH manual lists SOCKS4 and SOCKS5 as the supported protocols. By default the port listens on localhost only, so other people on your network cannot use it.

Point a client at it and check the exit IP:

curl --socks5-hostname 127.0.0.1:1080 https://ipv4.unknownproxies.com/ip

Stop the tunnel with Ctrl+C. It is a good fit for one person routing a browser or script through a server. It is a poor fit for a team, because every user needs SSH access to the box.

What a self-hosted proxy cannot do

A self-hosted proxy on a VPS also has a datacenter IP. Sites that limit hosting traffic treat it like any other datacenter IP. If you need consumer or ISP IP space, a self-built server cannot give you that.

FAQ

Do I need to create my own proxy server?

Usually, no. If you bought proxies from a provider, the proxy server already exists. Your job is to configure the endpoint correctly in your browser, bot, scraper, or script. Run your own server, for example with Squid, only when you control a machine whose IP you actually want to use.

How do I set up a proxy server on Windows?

Open Settings > Network & internet > Proxy, select Set up next to Use a proxy server, turn it on, enter the address and port, and select Save. For SOCKS5, use the app's own proxy settings instead.

What proxy format should I use?

Use the format your tool expects. Common options are host:port:username:password, http://username:password@host:port, and socks5://username:password@host:port.

How do I turn off a proxy server?

On Windows 11, open Settings > Network & internet > Proxy and switch off Use a proxy server and Use setup script. On a Mac, uncheck each proxy type under Details > Proxies. In a bot or script, remove the proxy field or variable and restart the task.

Should I use HTTP or SOCKS5 proxies?

Use HTTP(S) for most browsers, web scrapers, bots, and API clients. Use SOCKS5 when the app specifically asks for SOCKS or needs a generic tunnel.

Why does my proxy work in cURL but not in my bot?

The bot may require a different proxy format, a protocol dropdown, separate auth fields, or a different session mode. Test one proxy at a time and change only one setting between tests.

Can I use the same proxy for every account?

For account workflows, avoid sharing one proxy identity across many accounts unless the site naturally expects that behavior. Map accounts, profiles, and sticky sessions consistently.

Final thoughts

Get the host, port, credentials, protocol, and format right before anything else. Test one proxy in one client against an IP-check endpoint, then against the real target. Pick the proxy type by session needs: stable ISP IPs for accounts and checkouts, rotating residential for independent requests. Most failures at scale trace back to a format, protocol, or session mismatch that a single test would have shown.

Technical references: MDN Proxy servers and tunneling, curl proxy documentation, and Playwright HTTP proxy documentation.