Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Proxy unable to bind to "all interfaces"

Hello | Last updated: Jan 21, 2016 09:20PM UTC

I'm able to bind to "all interfaces" if I use port 8081. Or 8082. Or 808 or anything for that matter. But if I try to bind to "all interfaces" using port 8080, it fails. (UI doesn't allow me to tick the checkbox under the column "Running".) What is causing this problem? Why am I unable to bind to "all interfaces" using port 8080?

PortSwigger Agent | Last updated: Jan 22, 2016 09:07AM UTC

This is probably happening because you have another service already bound to port 8080 on at least one interface.

Burp User | Last updated: Jan 23, 2016 05:00AM UTC

There isn't one. I verified this with ` netstat -ano|find "8080" ` I had restarted Burp too. I don't see any problems with other numbers, simply "8080". Do you reckon this is a Burp bug?

Burp User | Last updated: Jan 23, 2016 05:01AM UTC

(Windows 8.1 Core)

PortSwigger Agent | Last updated: Jan 25, 2016 08:58AM UTC

It's not a Burp bug. Something is stopping Burp binding to that port on all interfaces. Burp performs the same operation regardless of the chosen port.

Burp User | Last updated: Oct 25, 2017 08:45PM UTC

Did you got the answer??

Burp User | Last updated: Sep 06, 2018 07:04PM UTC

If you haven't determined this yet; it is likely your enterprise anti-virus or other interface that doesn't let you bind the proxy to that port. I generally use something pretty off from that; like 1900. Your security policy may not allow you to use any port; even set to your loopback interface.

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