If you are trying to intercept traffic and Burp Suite is not cooperating, the problem is usually a misconfiguration rather than a broken installation.
This guide explains how to fix Burp Suite not working by checking the most common causes step by step, from proxy settings to TLS interception.
What “Burp Suite not working” usually means
Burp Suite can fail in different ways, and the fix depends on the symptom.
You might see no traffic in the Proxy tab, browser requests may bypass Burp, HTTPS pages may fail to load, or Burp itself may crash, freeze, or refuse to start.
Because Burp Suite is built around a local proxy, Java runtime, browser configuration, and certificate trust chain, a single broken link in that chain can stop interception entirely.
The fastest way to resolve it is to identify where the traffic is failing.
Check whether Burp Proxy is actually listening
Start with the simplest cause: Burp may not be listening on the port your browser is using.
In Burp Suite, go to the Proxy settings and confirm the listener is enabled on the correct interface and port, commonly 127.0.0.1:8080.
- Confirm the proxy listener is enabled.
- Verify the port matches your browser proxy settings.
- Check whether another app is already using that port.
- If needed, switch to a different unused port such as 8081.
If Burp is bound to 127.0.0.1 only, it will accept traffic from the local machine but not from other devices on the network.
If you are testing a mobile device or another host, change the bind address carefully and ensure firewall rules permit the connection.
Verify browser proxy settings
One of the most common reasons Burp Suite appears to be broken is that the browser is not pointed at Burp at all.
Set the browser’s HTTP and HTTPS proxy to the Burp listener address and port, or use Burp’s built-in browser to eliminate manual configuration errors.
Common browser configuration mistakes
- Proxy set for HTTP but not HTTPS.
- System proxy disabled after a browser update.
- Proxy extension overriding manual settings.
- Using a different browser profile that has its own network settings.
For Firefox, check network proxy settings in the browser preferences.
For Chrome and Edge, verify the operating system’s proxy settings, because they often rely on the system-wide configuration.
Fix HTTPS interception and certificate errors
HTTPS issues are the most frequent Burp Suite failure point.
If you can see HTTP traffic but HTTPS sites fail, the Burp CA certificate is usually not trusted by the browser or target device.
Install the Burp Suite CA certificate in the browser or OS trust store, then make sure the browser is using the intercepted connection rather than rejecting Burp’s generated certificate.
In Burp’s built-in browser, this is typically simpler because the trust setup is handled automatically.
Signs the certificate chain is the problem
- Browser shows certificate warnings or privacy errors.
- Sites load partially but login pages fail.
- Only HTTP works, while HTTPS never appears in Burp.
- Mobile apps or APIs reject the connection immediately.
Modern applications may also use certificate pinning.
In that case, Burp may be configured correctly, but the application intentionally refuses interception.
Testing pinned apps often requires a different approach, such as controlled test builds or approved instrumentation in a lab environment.
Check Java and Burp Suite installation health
If Burp will not start, crashes on launch, or opens to a blank window, the issue may be related to Java, memory allocation, or a corrupted installation.
Burp Suite runs on Java, so an incompatible runtime can prevent the interface from loading properly.
Make sure you are using a supported version of Burp Suite for your operating system and that the bundled or installed Java environment is intact.
If the application was manually upgraded or moved, reinstalling or replacing the launcher often resolves startup problems.
- Confirm your operating system is supported.
- Check that Burp’s bundled Java is present.
- Increase allocated memory if Burp hangs on large projects.
- Reinstall Burp if files appear corrupted.
If you use Burp in a resource-constrained environment, high memory usage can cause apparent freezes.
Closing large site maps, removing old project data, and allocating more RAM can improve stability.
Eliminate interference from VPNs, firewalls, and security software
Network security tools can block local proxy traffic or rewrite connections in ways that interfere with Burp Suite.
VPN clients, endpoint protection, antivirus tools, and corporate firewalls may prevent the browser from reaching the Burp listener or block Burp from reaching target sites.
Temporarily disable conflicting software in a safe test environment, then try again.
If Burp starts working after the change, add explicit allow rules rather than leaving security software disabled.
Things to inspect on the system
- Local firewall rules for the Burp port.
- VPN split tunneling behavior.
- Endpoint detection and response tools.
- Corporate proxy policies that override local settings.
On managed devices, local policy may force traffic through another proxy.
In that case, Burp may need to be configured as an upstream proxy or used within an approved testing network.
Make sure your browser is not bypassing the proxy
Some browsers and applications ignore manual proxy settings for certain destinations.
Common bypass rules, localhost exceptions, or proxy auto-configuration files can send traffic around Burp Suite without any visible error.
Review the browser’s PAC file, proxy exception list, and “no proxy for” rules.
Also check whether the target domain resolves to an internal address that the system treats differently from public traffic.
If only some sites are missing from Burp, bypass rules are a strong suspect.
Troubleshoot mobile and remote device interception
Intercepting traffic from phones, tablets, or virtual machines introduces extra variables.
The target device must trust Burp’s certificate, be configured to use the Burp host as its proxy, and be able to reach that host over the network.
- Use the machine’s LAN IP, not 127.0.0.1, for remote devices.
- Confirm the phone and Burp host are on the same network.
- Allow the port through the host firewall.
- Install the Burp CA certificate on the device.
For Android testing, system-wide interception may still fail if the app uses network security configuration or certificate pinning.
On iOS, trust settings and device management profiles can also affect interception.
Use Burp’s built-in tools to isolate the fault
Burp Suite includes diagnostic features that can save time.
The Proxy history helps confirm whether any traffic reaches Burp at all, while the Event log can reveal listener errors, certificate problems, or connection failures.
Repeater is also useful for testing whether Burp can send traffic out successfully once it receives a request.
If you see requests in the browser but not in Burp, the problem is before the proxy.
If requests appear in Burp but not in the target application, the issue is likely certificate, upstream connectivity, or filtering by the target.
Quick checklist for how to fix Burp Suite not working
- Confirm Burp Proxy listener is enabled and on the correct port.
- Point the browser or device proxy to Burp.
- Install and trust the Burp CA certificate.
- Check for certificate pinning in the target app.
- Verify Java, memory, and installation integrity.
- Disable or adjust VPN, firewall, and security software.
- Review proxy bypass rules and PAC files.
- Use Burp’s event log and proxy history to isolate the break point.
Working through these checks in order usually reveals the cause quickly and keeps debugging focused on the exact layer that is failing.