Use this browser proxy configuration guide to configure a proxy, review Windows proxy settings, macOS proxy settings, and Linux proxy configuration, then test the proxy connection.<\/p>\n
To configure a proxy, collect the endpoint, port, protocol, and authentication method; enter them in the application or operating-system proxy settings; then verify the observed egress IP and one HTTPS request. Browser settings may inherit the operating system, while Firefox and many developer tools can use independent settings. Configure only the traffic you intend to route.<\/p>\n
Before changing anything, save the current setting or take a private note that excludes the password. A typo in the protocol or port is more common than a broken server. If you are unsure whether the endpoint is HTTP or SOCKS5, consult the plan details and read the protocol comparison<\/a>.<\/p>\n Do not assume that a URL beginning with `https:\/\/` means an HTTPS destination proxy is required. Many providers call an HTTP proxy with CONNECT support an HTTP\/HTTPS proxy. The client still connects to the proxy using the configured proxy scheme, then tunnels HTTPS destination traffic.<\/p>\n Chrome, Edge, Brave, and many Chromium browsers normally open the operating-system proxy settings rather than maintaining a separate browser proxy profile. In Chrome, open Settings, search for proxy, and select the option to open your computer’s proxy settings. Configure the appropriate HTTP endpoint or system proxy there.<\/p>\n This can affect other applications that honor system settings. Browser extensions can manage profiles, but install only trusted extensions and verify which traffic they control. Chrome may prompt for proxy credentials when the endpoint requests authentication. Do not let a shared device save production credentials in a general password store.<\/p>\n Firefox can use its own connection settings. Open Settings, search for Network Settings, and choose Settings. Select Manual proxy configuration. For an HTTP endpoint, enter the HTTP Proxy and port and decide whether to use it for HTTPS as well. For SOCKS, enter the SOCKS Host and select SOCKS v5 when that is the assigned protocol.<\/p>\n Firefox includes an option to proxy DNS when using SOCKS v5. Enable it when remote resolution is required and supported. A local bypass list can keep `localhost`, `127.0.0.1`, and approved internal domains direct. Save, open a new private window, and verify the route.<\/p>\n On current Windows versions, open Settings, Network & Internet, then Proxy. A manual setup typically accepts an address and port for HTTP-aware applications. Add only necessary exclusions, and do not route local addresses through a public proxy. Windows system settings do not force every application or background service to use the proxy.<\/p>\n Some command-line and service applications use WinHTTP rather than the interactive user settings. Others have their own proxy fields or environment variables. Verify the actual application instead of treating the Windows screen as a universal tunnel. If all device traffic needs controlled routing, a proxy setting may not be the correct tool.<\/p>\n Open System Settings, Network, select the active connection, open Details, and choose Proxies. macOS can configure Web Proxy (HTTP), Secure Web Proxy (HTTPS), and SOCKS Proxy separately. Enter the server, port, and credentials if the operating policy allows storing them. Apply the settings, then test the intended browser and application.<\/p>\n Because settings belong to a network service, switching from Wi-Fi to Ethernet or another network may use a different configuration. Review the bypass field for local and corporate hosts. Remove the proxy cleanly when testing is complete rather than leaving an unreachable endpoint enabled.<\/p>\n GNOME, KDE, and other desktops provide system proxy panels, but application adoption varies. Browsers may follow the desktop setting, while package managers and command-line programs often use their own configuration. Environment variables are common for developer tools:<\/p>\n Variable names may be case-sensitive in a specific tool, and putting credentials directly in them can expose secrets to child processes or diagnostics. Use a protected configuration or secret mechanism where supported. For SOCKS, check the application’s own scheme syntax; not every program understands a SOCKS environment variable.<\/p>\n curl is useful because it reports protocol and HTTP errors clearly. Prefer an interactive prompt or protected config over a password in shell history. A basic HTTP proxy test without credentials looks like:<\/p>\n For a SOCKS5 endpoint with proxy-side hostname resolution:<\/p>\n Use `–proxy-user` only in a protected context. First request a simple HTTPS endpoint, then an IP-echo service you trust, and finally the real destination at a conservative rate. A successful IP check does not prove that every destination permits the traffic.<\/p>\n If any step fails, avoid changing multiple variables at once. The step-by-step troubleshooting guide<\/a> starts at network reachability and moves upward through authentication and destination responses.<\/p>\n After selecting an appropriate plan, use the host, port, protocol, and authentication details supplied for that allocation. Mexela lists fixed HTTP\/SOCKS endpoints in its private proxy plans<\/a>. Confirm the current instructions in the client area and keep credentials out of screenshots or public support messages.<\/p>\nInformation you need before setup<\/h2>\n
\n
Configure Chrome and Chromium-based browsers<\/h2>\n
Configure Firefox independently<\/h2>\n
Configure Windows system proxy settings<\/h2>\n
Configure macOS<\/h2>\n
Configure Linux desktops and environment variables<\/h2>\n
export HTTP_PROXY=http:\/\/proxy.example:port\nexport HTTPS_PROXY=http:\/\/proxy.example:port\nexport NO_PROXY=localhost,127.0.0.1,.internal.example<\/code><\/pre>\nTest with curl without leaking secrets<\/h2>\n
curl --proxy http:\/\/proxy.example:port https:\/\/example.com\/ -I<\/code><\/pre>\ncurl --proxy socks5h:\/\/proxy.example:port https:\/\/example.com\/ -I<\/code><\/pre>\nVerification checklist<\/h2>\n
\n
Common configuration mistakes<\/h2>\n
\n\n
\n \nSymptom<\/th>\n Likely mistake<\/th>\n Next check<\/th>\n<\/tr>\n<\/thead>\n \n Immediate handshake error<\/td>\n HTTP client pointed at a SOCKS port or the reverse<\/td>\n Confirm protocol and assigned port<\/td>\n<\/tr>\n \n HTTP 407<\/td>\n Missing or rejected proxy authentication<\/td>\n Check credential method and encoding<\/td>\n<\/tr>\n \n Works in Firefox, fails in Chrome<\/td>\n Firefox uses manual settings while Chrome uses the OS<\/td>\n Compare proxy scope<\/td>\n<\/tr>\n \n IP changed but DNS location did not<\/td>\n DNS resolved locally<\/td>\n Test supported remote DNS mode<\/td>\n<\/tr>\n \n Some applications connect directly<\/td>\n They ignore system settings<\/td>\n Use application-specific configuration<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n Using a Mexela endpoint<\/h2>\n