Burp Suite Browser Not Launching: 7 Causes, in Order

Clicking Open browser does nothing, or the window closes instantly. The seven real causes in order — root on Linux, missing Chromium libraries, quarantine, EDR.

Burp starts, the proxy listener comes up, and then you click Open browser and nothing happens. Sometimes a window flashes and closes. Sometimes there is a spinner that never resolves. On Linux it is usually silent; on macOS you get a dialog; on Windows you get an antivirus notification you did not read.

Burp’s embedded browser is a bundled Chromium, so the failures are Chromium failures — and Chromium is unusually explicit about why it refuses to start, provided you are looking at the right place to read its complaint.

Find the error before changing settings

Two places record a browser launch failure. Check both:

  1. The terminal you launched Burp from. Start Burp from a shell rather than from the desktop icon — ./BurpSuiteCommunity on Linux, or the launcher script in the Burp directory — so that stderr reaches your screen. Chromium’s own error text lands there.
  2. Burp’s event log. In the Dashboard tab, open Event log. Browser start failures and the reason are recorded as events.

Almost every cause below produces a recognisable line in one of those two places. Guessing at settings without reading it turns a two-minute fix into an afternoon.

Message you seeCauseGo to
Running as root without --no-sandbox is not supportedBurp is running as root on LinuxCause 1
error while loading shared libraries: libnss3.so (or libgbm, libasound, libatk)Missing Chromium dependenciesCause 2
Missing X server or $DISPLAYNo graphical sessionCause 3
Burp Browser cannot be opened, macOS dialogGatekeeper quarantineCause 4
Process starts and exits immediately, no messageBlocked by endpoint security, or a corrupt installCause 5 or 6
Browser opens but every site fails to loadNot a launch failure — the proxy path is wrongThe last section

1. Linux: Burp is running as root

The most common cause on Kali, and the one with the most misleading symptom: no error dialog in Burp at all, just a browser that never appears.

Chromium refuses to start as root without disabling its sandbox, because a browser running as root with sandboxing off is a privilege-escalation primitive pointed at your own machine. On Kali it is easy to end up here without noticing — a lot of the documentation assumes a root shell, and sudo burpsuite is a habit.

The correct fix is to stop running Burp as root. Run it as your normal desktop user. If you installed Burp into a root-owned directory, move it somewhere your user can execute, or run the installer as that user.

There is a workaround for the case where root really is unavoidable — a container, a throwaway VM: Settings → Tools → Burp’s browser → Allow Burp’s browser to run without a sandbox. Understand what that does before ticking it. It removes the process sandbox from a browser that is, by design, pointed at hostile web applications. A throwaway VM against a target you are authorised to test is the situation it is for; a daily-driver machine is not.

2. Linux: the Chromium libraries are not installed

Burp bundles Chromium but not the system libraries Chromium links against. A minimal Debian, a headless Kali install, or a container image without a desktop environment will be missing most of them.

The fastest way to see the full list is to run the bundled binary directly and read the loader’s complaint:

# The browser lives inside Burp's own directory
find ~/.BurpSuite/browser -name 'chrome' -type f 2>/dev/null
~/.BurpSuite/browser/*/chrome --version

Each run reports one missing library, then the next. Installing them on Debian and Kali:

sudo apt update
sudo apt install -y libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 \
  libdrm2 libgbm1 libasound2 libxkbcommon0 libxcomposite1 libxdamage1 \
  libxfixes3 libxrandr2 libpango-1.0-0 libcairo2 libatspi2.0-0

Package names drift between Debian releases — libasound2t64 on newer Ubuntu, for example. If apt reports a package as unavailable, install the rest and run the binary again; the loader names exactly what is still missing.

3. There is no graphical display

Chromium needs a window system. If you are on a headless server, inside WSL without WSLg, or connected over plain SSH, there is nothing for it to draw on and it exits.

The error is explicit: Missing X server or $DISPLAY. Confirm your environment:

echo "DISPLAY=$DISPLAY WAYLAND_DISPLAY=$WAYLAND_DISPLAY"
# both empty = no graphical session

Three ways forward, and the first is usually right:

  • Run Burp on the machine with the screen. Testing is interactive work; a desktop is the correct environment for it.
  • X11 forwarding over SSH — ssh -X with an X server running locally. It works but is slow enough that the browser feels broken.
  • Skip Burp’s browser entirely and point your local browser at the remote proxy — see the fallback section below. This is what most people doing remote testing actually do.

4. macOS: Gatekeeper is quarantining the browser

macOS tags files downloaded from the internet with a quarantine attribute, and it treats the bundled Chromium as an app the first time it runs. The result is a dialog saying the browser cannot be opened because Apple cannot check it for malicious software, or a silent exit.

Check whether the quarantine flag is present:

xattr -l ~/.BurpSuite/browser/*/Burp\ Browser.app | grep quarantine

If it is, clear it and launch Burp again:

xattr -dr com.apple.quarantine ~/.BurpSuite/browser

If macOS still blocks it, open System Settings → Privacy & Security and look for the message about the blocked app near the bottom of the window — there is an Open Anyway button there for the last blocked item.

5. Windows: endpoint security is killing it

Burp’s browser is an unsigned-off vendor Chromium build that launches from a directory most users have never heard of, which is a close match for how malware behaves. Antivirus, EDR and Windows’ Controlled Folder Access all react to that pattern.

Signs: the process starts and disappears, or the browser launches and is killed within a second, and the event log has nothing useful because the kill came from outside Burp.

Check your endpoint product’s protection history for a detection on the Burp browser path (%LOCALAPPDATA%\BurpSuite\browser). If it is there, add an exclusion for the Burp Suite directory — and be explicit with yourself about doing it: an exclusion on a directory is an exclusion on everything that ever gets written to it.

6. The browser installation is corrupt

An interrupted download leaves a partial Chromium that starts and dies. Burp downloads the browser on first use, and a flaky connection or a full disk produces exactly this.

Delete the browser directory and let Burp fetch it again:

# Linux and macOS
rm -rf ~/.BurpSuite/browser

# Windows (PowerShell)
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\BurpSuite\browser"

Then relaunch Burp and open the browser once. Watch the event log while it re-downloads — if it fails again, the cause is almost always network (a proxy intercepting the download) or disk space.

7. Disk space and temp directory permissions

Chromium needs room to write its profile and cache, and it needs /tmp to be writable. A full partition produces a launch failure with an unhelpful message, and it is common on VMs provisioned with a small disk.

df -h ~ /tmp
# and check the browser's own profile directory is owned by you
ls -ld ~/.BurpSuite

If Burp was ever run with sudo, ~/.BurpSuite may now be root-owned and unwritable by your normal user — another reason cause 1 is worth fixing properly rather than working around.

The fallback that always works: your own browser

Burp’s browser is a convenience, not a requirement. Any browser can be pointed at Burp’s proxy, and this route bypasses every launch problem above in one move.

  1. In Burp, confirm the proxy listener: Settings → Tools → Proxy → Proxy listeners. Note the interface and port.
  2. In your browser, set the HTTP and HTTPS proxy to 127.0.0.1 and that port.
  3. Install Burp’s CA certificate so HTTPS traffic is not rejected. With the proxy configured, browse to http://burp/ and download the certificate, then import it into your browser’s trust store.

For a browser you switch between proxied and direct, an extension such as FoxyProxy makes this a toggle instead of a settings trip. Use a separate browser profile for proxied work so that your normal browsing does not quietly flow through Burp.

A dedicated profile also protects you from the more expensive mistake: forgetting the proxy is on and logging into personal accounts through a tool that records every request.

If the browser opens but nothing loads

That is a different failure with a different cause list, and it is worth separating clearly:

  • Burp’s proxy listener is not running — the browser was configured to use a port nothing is listening on.
  • An upstream proxy is required — corporate networks need Burp itself configured to chain through their proxy: Settings → Network → Connections → Upstream proxy servers.
  • The browser’s proxy settings point at the old port — if you changed the listener port after first launch, Burp’s browser keeps the old value. Reset the browser settings in Settings → Tools → Burp’s browser.
  • HTTPS certificate not trusted — you get certificate warnings on every site, not a blank page. Install Burp’s CA.

Checklist

PlatformCheck firstCommand or setting
LinuxAre you root?id -u — 0 means yes
LinuxAre the libraries present?Run the bundled chrome binary directly
LinuxIs there a display?echo $DISPLAY
macOSIs it quarantined?xattr -l on the browser app
WindowsDid EDR kill it?Endpoint protection history
AnyIs the install complete?Delete the browser directory, relaunch
AnyIs there disk space?df -h
AnyDoes your own browser work?Set proxy to 127.0.0.1:8080

Frequently asked questions

Why does Burp’s browser not open on Kali when it worked before?

Most often because an update changed the bundled Chromium and it now needs a system library your install does not have, or because the previous run left a root-owned ~/.BurpSuite directory behind. Run the bundled binary from a terminal — the loader names the missing library or the permission problem directly.

Can I use Chrome or Firefox instead of Burp’s browser?

Yes, and many testers prefer it. Configure the browser’s proxy to Burp’s listener and install Burp’s CA certificate, and you have the same interception with a browser you already trust and know the developer tools of. The only thing you lose is Burp’s automatic proxy configuration and its isolated profile.

Is it safe to run Burp’s browser without the sandbox?

In a disposable VM pointed at an authorised target, the trade-off is acceptable. On the machine where you read your email, it is not: the browser exists to load hostile content, and the sandbox is the layer that stops a browser exploit from becoming a host compromise. Fix the root problem instead.

The browser opens but HTTPS pages fail with a certificate warning. Why?

Burp re-signs HTTPS traffic with its own CA, and the browser does not trust it yet. Burp’s own browser is configured automatically; an external browser needs the certificate installed. Browse to http://burp/ through the proxy, download the CA, and import it into the browser’s trusted authorities.


Keep reading

Related articles

Browse all articles