Burp Suite User Forum

Create new post

How to relaunch Burp Enterprise after restarting machine

Noah | Last updated: Oct 31, 2018 03:05PM UTC

I'm trying to relaunch Burp Enterprise after restarting my machine. I've found the JAR file, but every time I try to open any JAR file I'm prompted for Burp Professional License Key. How do I launch this so I can access the web interface?

Liam, PortSwigger Agent | Last updated: Oct 31, 2018 03:07PM UTC

The Burp jar file is part of the Enterprise file, however, that isn't how you launch the Enterprise Edition. You launch Burp Enterprise in a browser: - https://portswigger.net/burp/documentation/enterprise/getting-started/installation#post-installation-configuration Carry out the following steps to complete the installation: Browse to the web server on the relevant host and port (the default port is 8080). Log in using the credentials for the administrator account that were specified during installation. Have you tried using your browser using the relevant host and port? You should have configured this during the installation process (wizard).

Burp User | Last updated: Oct 31, 2018 03:58PM UTC

I saw the answer you posted similar to this. I've already ran through the post installation configuration. I've got multiple scans already. The issue is that the server isn't running after restart.

Liam, PortSwigger Agent | Last updated: Oct 31, 2018 04:30PM UTC

Sorry Noah, just to clarify, you're trying to open the .JAR file to start the server?

Burp User | Last updated: May 09, 2019 09:19AM UTC

I have the same issue. Rebooted my server and now none of the burpsuite services are actually working. All are showing as running but they are consistently trying to spawn instances of the host.sh script and that is failing with no indication why. This means that the web interface doesnt respond (connection refused). Netstat doesnt even show the ports as being open. Any ideas?

Rose, PortSwigger Agent | Last updated: May 09, 2019 10:29AM UTC

Please could you send an email to support@portswigger.net with the following log files: supervisor_enterpriseAgent.log supervisor_enterpriseServer.log supervisor_webServer.log You should be able to find these in /var/log/BurpSuiteEnterpriseEdition

Burp User | Last updated: May 09, 2019 03:47PM UTC

Hey, I plan to file a support ticket/report for this sure. Logs didnt really give any indication of a specific issue other than it trying to spawn thousands (literally hit 30k) of child processes because each one failed. Ive cleaned them out now because they hit 5GB But I found that the issue was that the automatic update kicked in and fundamentally broke the installation. Several files in the burp directory had been wiped clean. This was going between 1.0.14 to 1.0.15.

Rose, PortSwigger Agent | Last updated: May 10, 2019 09:18AM UTC

Thanks for the update. We'll take a look at the logs when you send them over.

Tamas | Last updated: May 08, 2020 06:14PM UTC

Hi, what is the purpose of this forum if you're solving the issue through email? Please add possible solutions here for others to find

Liam, PortSwigger Agent | Last updated: May 11, 2020 07:22AM UTC

Tamas, we endeavor to solve as much of the issue as possible via the forum. Sometimes we need to discuss sensitive information or send and receive certain files via email. Are you encountering a similar issue?

The | Last updated: May 25, 2020 09:30AM UTC

Is there a service that can be restarted or do i have to try and reinstall burp again? If i find the solution i'll post it.

Liam, PortSwigger Agent | Last updated: May 25, 2020 10:02AM UTC

John, what is the issue you have encountered?

The | Last updated: May 25, 2020 10:29AM UTC

Actually i solved it. I had to delete all traces of burp enterprise (because it wouldn't let me uninstall). Then create a new mysql database using different ports and names. Then reinstall burp ent. Supprise to say it worked.

Liam, PortSwigger Agent | Last updated: May 25, 2020 11:10AM UTC

Thanks for letting us know, John. Please let us know if you need any further assistance.

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