Configuring Proxy Settings for Interception
The first step in making Chrome work with Burp Proxy is establishing a communication channel between your browser and the Burp Suite application. Burp Suite acts as a man-in-the-middle proxy, meaning it sits between your browser and the internet to inspect, modify, and log HTTP/HTTPS traffic. To achieve this, you must configure Chrome to route its network requests through Burp's local listener.
Open Google Chrome and navigate to chrome://settings/system. Locate the option labeled "Open proxy settings" and click it. This action will open your operating system’s network configuration window rather than Chrome's internal settings. In Windows, this opens the Internet Properties dialog; on macOS, it opens Network preferences. Ensure that the "Manual proxy setup" is selected and enter 127.0.0.1 (or localhost) as the address and 8080 as the port. This is the default listening port for Burp Suite Community and Professional editions.
If you are using a Mac, ensure that the "Use SSL proxying" box is checked if you intend to intercept HTTPS traffic. After saving these settings, return to Chrome and reload any page. You should see a connection refused error or a blank page if Burp is not running, confirming that the proxy setting is active. If Burp is running, the request will be intercepted, and you will see the activity in the Burp Suite "Proxy" > "HTTP history" tab.
Installing the Burp Certificate Authority
Simply configuring the proxy is insufficient for modern browsers because they enforce strict security protocols regarding encrypted connections. When Chrome attempts to connect to an HTTPS site via Burp, Burp generates a temporary certificate on the fly to establish the secure tunnel. Since this certificate is signed by Burp's own Certificate Authority (CA) and not a trusted root like DigiCert or Let's Encrypt, Chrome will block the connection with a security warning.
To resolve this, you must manually install the Burp CA certificate into your system's trust store. In Burp Suite, go to the "Proxy" tab and select the "Options" sub-tab. Under the "Certificate Generation" section, click the "CA Certificate..." button. This will download a file named burpca.crt.
For Windows Users: Double-click the downloaded burpca.crt file. Click "Install Certificate," choose "Local Machine," and select "Place all certificates in the following store." Browse to "Trusted Root Certification Authorities." Restart Chrome completely to apply the changes. You can verify success by visiting http://burpsuite.com; if the certificate is installed correctly, the page will load without warnings.
For macOS Users: Open Keychain Access and drag the burpca.crt file into the "System" keychain. Right-click the certificate, select "Get Info," expand "Trust," and set "When using this certificate" to "Always Trust." You may need to restart Chrome. On newer versions of macOS, you might also need to clear the DNS cache or reboot the system for the trust chain to fully propagate.
Troubleshooting Common Connectivity Issues
Even with correct settings, users often encounter issues where Chrome appears to ignore the proxy or fails to load pages. One common cause is conflicting proxy configurations. If you have other tools running, such as Fiddler or Charles Proxy, they may be hijacking port 8080 or overriding Chrome's settings. Ensure that only one proxy tool is active at a time on the same port.
Another frequent issue arises from Chrome's built-in security features. Chrome has a feature called "Secure DNS" which bypasses the system proxy for DNS resolution. To fix this, go to chrome://settings/security and disable "Use secure DNS." Alternatively, you can configure Secure DNS to use your provider instead of automatic selection. Additionally, check if any Chrome extensions are interfering with network requests. Disable extensions temporarily to isolate the problem.
If you are working behind a corporate firewall, the firewall might be blocking outbound connections to localhost or specific ports. Consult your IT department to ensure that traffic on port 8080 is allowed for loopback addresses. Furthermore, some websites implement HSTS (HTTP Strict Transport Security) policies that prevent downgrade attacks. If you cannot connect to certain sites, try clearing your browser cache and cookies, as detailed in our guide on How to Change Cookie Settings on Chrome After Accepting All for a Site, to remove stale security headers.
Advanced Configuration and Best Practices
For more complex testing scenarios, you may need to exclude specific domains from proxying. In Burp Suite, go to "Proxy" > "Options" and add entries to the "Excluded in scope" list. This prevents Burp from intercepting traffic to those domains, which can speed up browsing and reduce unnecessary load on your machine. Conversely, you can define the "Target Scope" to limit interception only to the applications you are actively testing.
It is also important to manage the Burp Suite memory usage. Intercepting high volumes of traffic can consume significant RAM. If Chrome becomes unresponsive while Burp is running, consider increasing the Java heap size allocated to Burp Suite in the startup configuration. Regularly save your session data to prevent loss of captured requests during unexpected crashes.
Finally, remember that modifying system-wide proxy settings affects all applications, not just Chrome. If you need to switch back to normal browsing frequently, consider using Chrome's command-line flags or a proxy switching extension for quicker toggling. For developers interested in deeper inspection of web elements, exploring Chrome Extension to Inspect the JS Code Events of Any DOM Element can complement your proxy-based debugging workflow.
Frequently Asked Questions
Why does Chrome show NET::ERR_CERT_AUTHORITY_INVALID?
This error occurs because Chrome does not trust the certificate generated by Burp Suite. You must install the Burp CA certificate into your operating system's trusted root store to resolve this issue.
Can I use Burp Proxy with Incognito mode?
Yes, Incognito mode respects system-level proxy settings. However, ensure that the Burp certificate is installed in the system keychain or certificate store, not just the user profile, to avoid permission issues in private windows.
How do I change the default Burp listening port?
You can change the port in Burp Suite under "Proxy" > "Options" > "Proxy Listeners." Update the port number there and correspondingly update your Chrome or OS proxy settings to match the new port.
Does Burp Suite slow down my browsing experience?
Intercepting and logging all traffic adds latency. Disabling interception for non-targeted sites in the "Excluded in scope" list significantly improves performance and reduces CPU/RAM usage.
What if I cannot access burpsuite.com after installing the cert?
If the test domain fails to load, your system may still be caching old DNS or certificate data. Try restarting your computer or flushing the DNS cache to force the system to recognize the new trust anchor.