How to Fix Burp Suite Proxy Not Intercepting

In this tutorial, you'll learn about How to Fix Burp Suite Proxy Not Intercepting. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Burp Suite shows no traffic in the Target or Proxy tabs. The browser is not sending traffic through the Burp proxy.

The Wrong Way

// Setting the browser proxy to 127.0.0.1:8080 but not installing the CA cert
// HTTPS traffic fails with certificate warnings and is not intercepted

Without the Burp CA certificate, the browser refuses to send HTTPS traffic through the proxy.

The Right Way

Step 1: Verify the proxy listener is running

# Burp Suite → Proxy → Proxy Settings
# Check:
# - "Running" is checked
# - Listener: 127.0.0.1:8080
# - "All interfaces" for external devices

Step 2: Configure browser proxy

# Firefox:
# Settings → Network Settings → Manual proxy
# HTTP Proxy: 127.0.0.1, Port: 8080
# Check "Also use this proxy for HTTPS"

# Chrome/Firefox extension:
# Install "FoxyProxy" or "SwitchyOmega"
# Create a Burp profile: 127.0.0.1:8080

Step 3: Install the Burp Suite CA certificate

# Once proxy is configured:
# Visit: http://burpsuite
# Click "CA Certificate" → download `cacert.der`

# Firefox: Settings → Privacy & Security → Certificates → Import
# Chrome: Settings → Security → Manage Certificates → Import
# Check "Trust this CA to identify websites"

Step 4: Disable intercept or set scope

# If Intercept is ON, requests are paused until forwarded
# Toggle: Proxy → Intercept → "Intercept is off"
# Or set scope:
# Proxy → Options → "Intercept Client Requests" → "Only items within scope"

Burp Proxy now shows HTTP/HTTPS traffic — GET requests visible in Target tree, intercept toggles work.

Prevention

• Always install the Burp CA certificate before starting an engagement.
• Use a dedicated browser profile for Burp testing to avoid mixing with personal browsing.
• The proxy interception model is the foundation of Durga Antivirus Pro's HTTP monitoring — all traffic passes through a local proxy for inspection.

Common Mistakes with suite proxy not intercepting

1. Mixing let bindings with <- bindings in do notation, producing type errors
2. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
3. Non-exhaustive pattern matches that compile with warnings then crash at runtime

These mistakes appear frequently in real-world BURP code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ