How to Set Up a Proxy: Windows, Mac, Chrome and Firefox

By Marcus Reiner · 2026-07-27 · 9 min read · Education

Start with the settings for your actual browser or app, then verify the connection. This guide explains proxy setup, common failures and what a proxy does not protect.

Quick answer: how do you set up a proxy?

Get the protocol, host, port and authentication method from your network administrator or proxy provider. On Windows 11, open Settings > Network & internet > Proxy. On a Mac, open System Settings > Network > your active connection > Details > Proxies. Enter the endpoint, save the settings, and verify the public IP in the same app you intend to use.

Chrome normally follows the operating system proxy configuration on Windows and macOS. Firefox can use its own settings. Neither an operating system proxy setting nor a changed IP proves that every application, DNS query or WebRTC connection on your device uses that proxy. Choose the scope first; do not treat a browser proxy as a VPN.

Before you start: understand each proxy setting

The host is the server address, such as proxy.example.com. The port is a separate number supplied by the operator. When the interface has separate host and port fields, do not paste a complete URL, credentials or a protocol prefix into the host field unless the product explicitly requests it. Example values in this guide are placeholders, not working proxy credentials.

Authentication usually means a username and password or an allowlisted public IP. With IP allowlisting, register the public IP of the connection that will reach the proxy, not a private address such as 192.168.1.10. Mobile networks and changing home connections can invalidate that allowlist. Never share credentials in a screenshot, public support thread or shareable link.

HTTP proxies commonly tunnel HTTPS website connections using CONNECT. An HTTPS destination does not necessarily mean the connection to the proxy itself uses TLS. Confirm the endpoint protocol with the operator. SOCKS5 is a different protocol, and support for authentication and remote DNS varies by client. A PAC file is a script that chooses a proxy for matching destinations; only use one from a trusted administrator.

Windows 11: manual proxy setup and how to turn it off

Open Settings > Network & internet > Proxy. Under Manual proxy setup, choose Set up beside Use a proxy server. Enable it, enter the address and port, review any bypass exceptions, and save. Older Windows versions may show a direct toggle rather than a Set up dialog. For an administrator-provided PAC URL, use the setup-script option instead of inventing a manual server.

An application may prompt for credentials when it reaches the proxy. The Windows manual screen is not a universal username/password store, and not every application supports the same authentication method. If the browser cannot authenticate, consult the provider or administrator about supported credentials or IP allowlisting rather than repeatedly changing unrelated network settings.

To remove a manual proxy, return to the same screen, disable Use a proxy server and save. Disable a setup script only if it is not required by your organization. Managed settings may be enforced by policy. If settings return after you disable them on a personal computer, inspect installed extensions, VPN software and security software before assuming the proxy provider caused it.

macOS: configure the active Wi-Fi or Ethernet service

Open System Settings > Network, select the active service, choose Details and then Proxies. Enable the relevant protocol, supply the server and port, and enter credentials if the selected proxy option supports them. Confirm with OK or Done as shown by your macOS version. Older macOS releases use System Preferences and may require Apply.

Proxy settings belong to the selected network service. Configuring Wi-Fi does not automatically configure Ethernet. Likewise, enabling only Web Proxy (HTTP) is not the same as configuring all HTTPS destinations. Follow the operator's instructions for Web Proxy, Secure Web Proxy or SOCKS Proxy; the menu labels alone do not establish the endpoint's encryption guarantees.

To turn the proxy off, return to the same service and disable the proxy options you enabled. Reopen the browser and test again. If one application continues using a proxy, inspect its own settings and any background network software. Do not remove a managed corporate configuration without approval.

Chrome and Edge: use system settings or a reviewed extension

On Windows and macOS, Chrome and Edge normally use system network proxy settings. In Chrome, search Settings for proxy or open Settings > System > Open your computer's proxy settings. The button opens the operating system controls; it is not a separate Chrome-only proxy form. Enterprise policies and proxy extensions can override the normal behavior.

For browser-only control, a proxy management extension may be appropriate, but inspect its publisher, permissions and maintenance history. An extension that controls routing can access sensitive browsing information. Prefer a reviewed extension or an administrator-managed configuration, and remove conflicting switchers. A normal browser profile alone does not create independent proxy routing.

Keep HTTPS certificate verification enabled. A certificate warning is not a routine step to click through when setting up a commercial proxy. If an organization legitimately requires TLS inspection, installation of its certificate should follow its documented, approved process. Do not install a random certificate supplied by an unknown proxy operator.

Firefox: configure a browser-only HTTP or SOCKS proxy

Open Settings > General, scroll to Network Settings and select Settings. Choose Manual proxy configuration to enter an HTTP proxy or SOCKS host and port. The dialog also offers system proxy settings and automatic configuration. Read the current labels carefully: using the same proxy for HTTPS destinations and choosing SOCKS v5 are different options.

For SOCKS v5, Firefox exposes a Proxy DNS when using SOCKS v5 option. Enable it when you want destination hostnames resolved through that proxy and your endpoint supports the configuration. This is a Firefox setting, not a promise about every other program on the device. Authentication support also differs by protocol; verify the exact combination before buying a plan.

Review the No proxy for exceptions. A destination that matches an exception will not take the same route as an ordinary website. To undo the change, select No proxy or Use system proxy settings according to your intended configuration and save. Then test inside Firefox rather than relying on a result from Chrome.

Verify the proxy: a repeatable before-and-after check

First record the public IP with the proxy disabled. Enable the proxy, open our What Is My IP tool in that same browser and compare the result. A different public IP shows the route used for that specific request. With a corporate proxy or a proxy sharing your existing egress address, the IP may not change; ask the administrator what result to expect.

Next, load an HTTPS page, confirm there are no certificate warnings, and check the provider dashboard for session or traffic evidence if available. A country or city label comes from a geolocation database and can be inaccurate; it does not prove the physical location of the device or guarantee access to a regional service.

Use the Browser Fingerprint Checker for browser-exposed signals and available WebRTC candidate information. Treat a missing candidate as inconclusive, not as proof that no leak is possible. The IP tool does not independently test DNS routing, and a timezone mismatch is not proof of an IP leak. DNS verification requires an appropriate DNS test or network observation in the actual client.

Troubleshooting: match the symptom to the next check

Change one variable at a time. Save the exact error message and test a destination you are authorized to access. A reachable proxy and a destination refusing a request are separate problems; buying another pool before identifying the error can waste money.

• 407 Proxy Authentication Required: check credentials, account status and the allowed authentication method. Confirm the allowlisted source IP if applicable.
• Connection refused or timeout: verify host, port and protocol; check local firewall rules and whether the endpoint is reachable from this network.
• ERR_PROXY_CONNECTION_FAILED or a tunnel error: remove conflicting extensions and compare endpoint details with the operator's instructions.
• 403 from the destination: authentication to the proxy may have succeeded. Check permissions and the target's access policy; an IP change does not grant access.
• 429 Too Many Requests: slow down, respect Retry-After where present and reduce concurrency. Rotating IPs is not a substitute for permission.
• Unchanged public IP: confirm the correct browser, active configuration and bypass rules. Some apps ignore system proxy settings.
• Certificate error: stop and investigate the certificate chain or endpoint configuration. Never disable verification as a quick fix.

Python and command-line clients need their own configuration

Requests and command-line clients do not necessarily inherit the graphical operating system setup. For Python Requests, pass a proxies mapping with http and https destination keys. An HTTP proxy can be the value for both keys when it supports CONNECT. Use a request timeout and handle non-success status codes; a request that never finishes is not a useful verification test.

Keep the proxy URL in an environment variable or secret manager rather than committed source code. If credentials are embedded in a URL, encode the username and password separately so reserved characters such as @, : and / do not change its meaning. Avoid logging that URL in exceptions.

For curl, the distinction between socks5:// and socks5h:// matters: socks5h requests proxy-side hostname resolution. Do not assume that convention works identically in every library. Consult the client's documentation and test the same destination through the same protocol that your production job will use.

Choose the minimum setup you actually need

For workplace connectivity, use the organization's approved endpoint. For testing your own website, an application-specific proxy may be enough. For authorized location testing, choose the required country and verify it rather than purchasing the largest residential pool. Static or sticky sessions can help maintain a multi-step workflow, but their duration and availability depend on the operator.

Compare proxy providers only after confirming supported protocols, authentication, usage limits and refund terms. Our comparison page and cost calculator can help evaluate traffic costs; neither establishes that a provider will work on a particular target. Affiliate offers on this page are commercial links and do not replace those checks.

This guide is an editorial synthesis of platform documentation, not a claim that every OS version, network and provider has been independently tested. Follow the sources below for current interface details. A proxy changes routing for participating traffic; it does not automatically encrypt all device traffic, erase browser identity or make restricted activity permissible.

Frequently Asked Questions

Sources and further reading

• Microsoft: use a proxy server in Windows
• Apple: change proxy settings on Mac
• Mozilla: connection settings in Firefox
• Chromium: proxy support and authentication
• Requests: proxies and authentication
• curl: proxy protocol options

Put this guide into practice

• Check the public IP this browser exposes
• Inspect browser fingerprint and WebRTC signals
• Compare proxy providers and plan limitations
• Estimate retry-adjusted proxy traffic cost