Skip to main content
Questions Categories Search Providers
Troubleshooting

How to Check Proxy and Firewall Settings in Google Chrome [2026 Guide]

7 min read

How to Check Proxy and Firewall Settings in Google Chrome

As a senior proxy expert, I often see users confused about where Google Chrome stores its connection settings. Unlike Firefox, which allows you to configure proxies directly within the browser interface, Chrome delegates this responsibility to the underlying operating system. This guide will walk you through exactly how to inspect, audit, and troubleshoot these settings in 2025.

Understanding the Architecture: Chrome and Your OS

Before diving into the "how," it is crucial to understand the "why." Google Chrome uses the System Proxy and System Firewall settings by default. This design choice ensures that if you configure a secure corporate proxy or VPN at the OS level, Chrome adheres to it without requiring separate configuration.

However, this also means that malware or unauthorized software can potentially route your Chrome traffic through a rogue proxy server without you changing anything inside the browser itself. This makes checking these settings a vital part of cybersecurity hygiene.

---

Part 1: How to Check Proxy Settings

Method A: Using the Chrome Internal URL (The Quickest Way)

While Chrome doesn't have a graphical settings menu for proxies, it has a powerful internal debugging tool.

1. Open Google Chrome. 2. Type chrome://net-internals/#proxy into the address bar and hit Enter. 3. Interpreting the Data: * Effective Settings: This section displays the actual proxy server Chrome is using. If it says "Direct Connection," you are not using a proxy. * Script: If an automatic configuration script (PAC) is in use, the URL will be listed here. * Bypass List: Shows which websites are configured to ignore the proxy.

This tool is read-only but is the fastest way to audit what the browser "thinks" it should be doing.

Method B: Checking Windows Settings (Windows 10/11)

This is where the settings are actually controlled.

1. Click the Start button and type "Proxy." 2. Select Proxy Settings from the list (or go to Settings > Network & Internet > Proxy). 3. Automatic Setup: Check if "Automatically detect settings" or "Use setup script" is toggled on. If "Use setup script" is on, copy the script URL and analyze it; this is common in enterprise environments but rare for home users. 4. Manual Setup: Under "Manual proxy setup," look at the "Use a proxy server" toggle. If this is enabled, check the IP address and port. * *Warning:* If you see a local IP (like 127.0.0.1) and a port like 8080, you likely have a VPN or a proxy software (like AdGuard or a botting client) running. If you do not recognize the IP, disable it immediately.

Method C: Checking macOS Settings (macOS Sonoma & Sequoia)

1. Click the Apple Menu > System Settings. 2. Navigate to Network. 3. Select your active connection (Wi-Fi or Ethernet) and click Details. 4. Click the Proxies tab. 5. Here you will see protocols like HTTP, HTTPS, FTP, and SOCKS. * If any checkboxes are selected and an IP address is populated, your traffic is being routed.

---

Part 2: How to Check Firewall Settings

Google Chrome does not have a built-in firewall. It relies entirely on the operating system's firewall to allow or block incoming and outgoing connections. If Chrome cannot connect to the internet, it is often because the firewall is blocking the chrome.exe process.

Checking Windows Defender Firewall

1. Press the Windows Key, type "Firewall," and select Firewall & Network Protection. 2. Click Allow an app through Firewall. 3. Click the Change Settings button (requires Admin rights). 4. Scroll through the list to find Google Chrome. 5. Ensure that both Private and Public boxes are checked. If the Public box is unchecked, Chrome may fail to connect when you are at a coffee shop or public hotspot.

Checking macOS Application Firewall

1. Go to System Settings > Network. 2. Click Firewall. 3. Ensure Firewall is turned On. 4. Click Options. Verify that Google Chrome is set to "Allow incoming connections."

---

Advanced Troubleshooting for Proxy Experts

For the readers of ProxyFAQs, I want to provide a deeper technical look. Sometimes settings are hidden in the Registry or imposed by Group Policy, rendering the standard Settings menus useless.

The Registry Check (Windows)

If you suspect malware is forcing a "Proxy Server" setting that keeps turning itself back on, you need to check the Windows Registry.

1. Open the Run dialog (Win+R) and type regedit. 2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings 3. Look for a key named ProxyEnable: * 0x00000000 (0): Proxy is Disabled. * 0x00000001 (1): Proxy is Enabled. 4. Look for ProxyServer: This string value will contain the IP:Port (e.g., 10.10.1.10:8080).

If you did not set this, delete the ProxyServer string and change ProxyEnable to 0.

Environment Variables Check

Developers and power users sometimes set proxies via Environment Variables, which Chrome respects. This is common when using Python's requests library or terminal tools like curl.

1. Search for "Edit the system environment variables" in Windows. 2. Click Environment Variables. 3. Check User variables and System variables for: * HTTP_PROXY * HTTPS_PROXY * NO_PROXY

If these exist, Chrome will prioritize them over the GUI settings.

---

Verifying Connectivity with cURL/Python

As an automation expert, I often verify proxy settings using code rather than GUIs. This strips away the browser layers and shows the raw connection.

Python Verification Script

You can use this script to check if your system proxy is actually reachable.

import requests

import os


Check if environment variables are set


proxy_http = os.getenv('HTTP_PROXY') proxy_https = os.getenv('HTTPS_PROXY')


print(f"Detected ENV Proxy: {proxy_https or proxy_http}")


Attempt a request


try: # If using a direct proxy for testing (e.g., localhost:8080) # proxies = {'http': 'http://127.0.0.1:8080', 'https': 'http://127.0.0.1:8080'} # response = requests.get('https://httpbin.org/ip', proxies=proxies, timeout=5)


# Use system default (None) response = requests.get('https://api.ipify.org?format=json', timeout=5) print(f"Connection Successful. Public IP: {response.json()['ip']}") except requests.exceptions.ProxyError as e: print(f"Proxy Configuration Error: {e}") except Exception as e: print(f"Connection Failed: {e}")

Linux Terminal Verification

If you are on Linux or using WSL on Windows:

curl -v https://www.google.com

Look for the lines starting with * Uses proxy env var no_proxy or * Trying [IP Address]... to see exactly where the traffic is routed.

---

Summary Table: Proxy vs. Firewall

| Feature | Proxy Settings | Firewall Settings | | :--- | :--- | :--- | | Purpose | Routes traffic through an intermediary server. | Blocks/Allows connections based on rules. | Location | Windows: Settings > Network > Proxy | Windows: Firewall & Network Protection | | macOS: System Settings > Network > Proxies | macOS: System Settings > Network > Firewall | Chrome URL | chrome://net-internals/#proxy | N/A (Browser level has none) | Symptom of Issue | "ERR_PROXY_CONNECTION_FAILED" or specific sites not loading. | "ERR_CONNECTION_REFUSED" or "ERR_NETWORK_ACCESS_DENIED" | | Risk Level | High (Malware often enables rogue proxies). | Medium (Mainly blocks apps from running). |

Conclusion

To check your proxy and firewall settings for Google Chrome, you must look beyond the browser. Chrome is a reflection of your OS configuration. By checking the system Network settings, verifying the Windows Registry, and using chrome://net-internals, you can diagnose almost any connectivity issue.

For 99% of users, the "Automatic detect settings" should be ON, and the "Use a proxy server" toggle should be OFF, unless you are deliberately using a VPN or corporate tool.

Share: