Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Embedded browser does not connect to proxy when running second Burp instance

Barnaby | Last updated: Jul 26, 2021 03:31PM UTC

Version: Burp Suite Professional v2021.6.2 Unexpected behaviour - unsure if a bug, or a limitation of the proxy configuration mechanism for the embedded browser. When starting the embedded browser in a second instance of Burp, the software detected that the first Burp instance was present (using the default port of 8080), and started a proxy on port 8081. However, the embedded browser was still configured to connect to the proxy on port 8080, and traffic went to the incorrect Burp instance.

Hannah, PortSwigger Agent | Last updated: Jul 27, 2021 10:36AM UTC

Hi Thank you for reporting this. We are aware of this issue when two embedded browsers are running concurrently. If you have one embedded browser open on either installation, then the traffic will be directed appropriately. You can also set up an external browser to be used by Burp. Instructions on how to set this up can be found here: https://portswigger.net/burp/documentation/desktop/getting-started/proxy-setup

Ben, PortSwigger Agent | Last updated: Sep 02, 2021 10:08AM UTC

Hi Barnaby, The development team is still investigating a way to implement a long term fix for this particular issue but, In the meantime, we believe we have a workaround that will prevent this behaviour. If you navigate to the User Options -> Misc -> Embedded Browser section within Burp and then disable the 'Allow embedded browser to store settings and history' then this should allow you to launch a separate embedded browser for each running instance of Burp and direct any proxied traffic appropriately. We will, of course, update you when we have implemented a permanent fix for this issue.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.