Burp Suite on Parrot Linux: Install and Configure With Firefox

This Burp Suite guide is for authorized testing only: run it against your own machines, a home lab such as DVWA or Juice Shop, or platforms like Hack The Box and TryHackMe that explicitly allow it. Burp Suite on Parrot Linux is the most common way to inspect and modify the HTTP traffic between a browser and a web app, and on a fresh Parrot install it takes about ten minutes to go from nothing to a working proxy in Firefox. This guide walks through installing the Community edition, pointing Firefox at the proxy, trusting Burp’s CA certificate so HTTPS sites load without warnings, and fixing the handful of problems that trip up almost everyone on their first attempt.

What Burp Suite Does and Which Edition You Get on Parrot Linux

Burp Suite is an intercepting proxy. Your browser sends every request to Burp instead of straight to the server, Burp shows it to you, lets you edit it, and then forwards it. That one trick is the basis of almost all manual web application testing: you can change hidden form fields, replay a login with a different user ID, or watch exactly what an API returns when you send it something unexpected.

PortSwigger publishes three editions. Community is free and includes Proxy, Repeater, Decoder, Comparer and a throttled Intruder. Professional adds the automated scanner, full-speed Intruder, project saving and the extension store without limits. Enterprise is a separate server product for continuous scanning. Everything in this guide works with Community, which is what the Parrot repositories ship.

If you installed the Security edition, Burp Suite is normally already present. On Home edition it is not installed by default, but the same package is one apt command away.

Step 1: Install Burp Suite on Parrot Linux

Update the package index first, then install from the Parrot repository:

sudo apt update
sudo apt install burpsuite

Check that it landed:

which burpsuite
apt policy burpsuite

The second command tells you the installed version and which repository it came from, which is useful later when you decide whether to stay on the packaged build or switch to the upstream installer.

Launch it from the terminal (so you can see any Java errors) or from the applications menu under the web application analysis section:

burpsuite

On first launch you accept the licence, choose Temporary project (the only option in Community), keep Use Burp defaults, and click Start Burp. The main window should open within a few seconds.

Alternative: the official PortSwigger installer

The repository package can lag behind PortSwigger’s releases by weeks or months. If you need the newest features, or the packaged version refuses to start because of a Java mismatch, download the Linux installer from the official PortSwigger download page, then:

chmod +x burpsuite_community_linux_*.sh
./burpsuite_community_linux_*.sh

Run it as your normal user, not root. The installer bundles its own Java runtime, so it does not depend on whatever JDK is on the system. It creates a launcher in ~/BurpSuiteCommunity/ and a menu entry. You can keep both the apt package and the upstream build installed side by side; just be aware that running two instances at once will fight over port 8080.

Step 2: Confirm the Proxy Listener

Inside Burp, open Proxy → Proxy settings (older builds: Proxy → Options). The listener table should show one entry bound to 127.0.0.1:8080 with Running ticked. If port 8080 is taken by something else on your Parrot system, Burp will show the listener as not running. Find the culprit with:

sudo ss -ltnp | grep 8080

Either stop that service or edit the Burp listener to use a different port such as 8081. Whatever you pick, Firefox must use the same port in the next step.

Step 3: Configure Firefox to Use the Burp Proxy

You have two ways to do this. The manual method is fine for a lab machine; the extension method is better if you also use the same Firefox profile for normal browsing.

Option A: Manual proxy settings

  1. Open Firefox and go to Settings → General, scroll to Network Settings, click Settings….
  2. Select Manual proxy configuration.
  3. HTTP Proxy: 127.0.0.1, Port: 8080.
  4. Tick Also use this proxy for HTTPS.
  5. Clear the No proxy for box. Firefox adds localhost, 127.0.0.1 there by default, which means traffic to a lab app running on your own machine would bypass Burp entirely.
  6. Click OK.

Firefox has a hidden setting that still bypasses the proxy for loopback addresses even when the exclusion box is empty. If local targets never show up in Burp, open about:config, search for network.proxy.allow_hijacking_localhost, and set it to true.

Option B: FoxyProxy extension

Install FoxyProxy Standard from the Firefox add-ons site. Add a proxy with type HTTP, host 127.0.0.1, port 8080, and give it a name such as “Burp”. The toolbar icon then lets you flip between direct browsing and Burp with one click, which is far less annoying than reopening the settings dialog every time you finish a test session.

Test the connection

In Burp, go to Proxy → Intercept and make sure intercept is off for the moment. In Firefox, load any plain HTTP page, for example a DVWA instance from your home pentesting lab. Switch to Proxy → HTTP history in Burp. If the request appears there, the proxy chain works. HTTPS sites will still fail at this point, which the next step fixes.

Step 4: Install the Burp CA Certificate in Firefox

Burp decrypts HTTPS by generating a certificate for every site on the fly, signed by its own certificate authority. Firefox will refuse those certificates until you tell it to trust that CA.

  1. With the proxy active in Firefox, browse to http://burpsuite (plain http, no s). Burp serves a small page from the proxy itself.
  2. Click CA Certificate in the top right and save cacert.der to your Downloads folder.
  3. In Firefox open Settings → Privacy & Security, scroll to Certificates, click View Certificates….
  4. On the Authorities tab click Import…, select cacert.der.
  5. Tick Trust this CA to identify websites and confirm.

Now load an HTTPS page. It should render normally and show up in Burp’s HTTP history with the full decrypted request and response. If you later reinstall Burp or reset its settings, Burp generates a new CA and you have to repeat this import; the old entry (named PortSwigger CA) can be deleted from the same dialog.

Only import this certificate into a browser or profile you use for testing. A browser that trusts the Burp CA will trust any certificate Burp mints, so it is not something you want in the profile you use for online banking.

Step 5: Your First Intercepted Request

Turn intercept on under Proxy → Intercept. In Firefox submit a login form on your lab target. The browser will appear to hang while Burp holds the request. In the intercept panel you can edit any part of it: change a parameter value, add a header, alter a cookie. Click Forward to send the modified request, or Drop to discard it. Right-click and choose Send to Repeater to keep a copy you can resend and tweak as many times as you like without touching the browser again.

Two settings make day-to-day use much calmer:

  • Target → Scope: add your lab host, then under Proxy settings enable “only intercept in-scope items” so Firefox telemetry and extension update checks do not clutter the intercept view.
  • Proxy settings → Response interception: leave it off unless you specifically want to modify what the server sends back.

Troubleshooting Burp Suite on Parrot Linux

SymptomLikely causeFix
Burp never opens, terminal shows Java exceptionsSystem JDK too old or too new for the packaged buildUse the upstream installer, which carries its own runtime; or check java -version and sudo update-alternatives --config java
Firefox says “The proxy server is refusing connections”Burp not running, or listener on a different portStart Burp, confirm the listener under Proxy settings, match the port in Firefox
HTTPS pages show a certificate warningCA not imported, or Burp regenerated its CARepeat Step 4; remove the old PortSwigger CA entry first
Local lab app never appears in HTTP historyFirefox bypasses loopback addressesClear “No proxy for” and set network.proxy.allow_hijacking_localhost to true
UI text is tiny or blurry on a HiDPI screenJava scaling not picked upIn Burp open Settings → User interface → Display and raise the font size and scaling
Burp opens blank or crashes on KDE Plasma 6 (Wayland)Java AWT and Wayland compatibilityLog into an X11 session, or launch with GDK_BACKEND=x11 burpsuite

If the whole desktop feels sluggish while Burp runs, it is usually memory: Burp is a Java application that happily takes 1–2 GB. The tips in how to speed up Parrot Linux apply, and on a VM giving the guest 4 GB or more makes a real difference.

Keeping Burp Updated

For the repository build, Burp updates arrive with the rest of your system. Use the method described in how to update Parrot Linux safely; parrot-upgrade is the recommended wrapper, but a plain sudo apt update && sudo apt full-upgrade also pulls the new package. The upstream installer has its own updater under Help → Check for updates, and it will prompt you when a new build is out. You can see which build you are on at any time under Help → About.

Pairing Burp With the Rest of Your Toolkit

Burp covers the application layer. Before you reach it, you usually want to know what ports and services a target exposes, which is a job for Nmap. Once Burp has found an interesting endpoint, tools like sqlmap or ffuf can take over for automated testing of a single parameter or path. Burp’s Copy as curl command option (right-click on any request) is the easiest bridge between the GUI and those command-line tools.

FAQ

Is Burp Suite free on Parrot Linux?

Yes. The burpsuite package in the Parrot repository is the Community edition, which is free for personal use. Professional requires a paid licence from PortSwigger and is installed with the same upstream installer; you enter the licence key on first launch.

Do I have to use Firefox?

No. Burp ships its own embedded Chromium browser (Proxy → Intercept → Open browser) that is preconfigured with the proxy and CA certificate, so nothing in Steps 3 and 4 is needed for it. Firefox is still worth setting up because it keeps your testing browser separate and works better with extensions you may already rely on.

Why does Firefox still load some pages without going through Burp?

Almost always because of the loopback bypass described in Step 3, or because FoxyProxy is set to a pattern mode that excludes the host. Switch FoxyProxy to “use proxy for all URLs” while testing, and confirm with a request to http://burpsuite, which only resolves when the proxy is actually in the path.