Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Burp Proxy fails to load the page if browsed to a website with specific port # mentioned

Ekanath | Last updated: Jan 31, 2017 10:46AM UTC

I tried to connect to a web server with specific port number (ex., http://199.63.23.23:12030). Burp proxy failed to load and says "unable to connect". Where with same proxy configuration able to connect to same & other servers. pls help.

PortSwigger Agent | Last updated: Jan 31, 2017 11:43AM UTC

This simply indicates that Burp wasn't able to open a network connection to that host and port. Are you able to connect to this URL directly using your browser, without Burp as your proxy?

Burp User | Last updated: Mar 17, 2017 11:06AM UTC

yes.. it connects without proxy

PortSwigger Agent | Last updated: Mar 20, 2017 09:08AM UTC

Is Burp running on the same machine that you are able to connect directly to the application from? It sounds like the issues are around network connectivity, and we would suggest speaking to your technical admins to resolve any issues there.

Burp User | Last updated: Feb 08, 2018 10:26AM UTC

The same issue I am facing, the http://172.***.225.15:60 is accessible on the browser but when I proxying through Brup it is not loading properly. The burp's alert is showing "failed to conect 172.***.225.15:60.

Liam, PortSwigger Agent | Last updated: Feb 08, 2018 10:35AM UTC

If you see connection failure messages for every request, then this suggests that Burp isn't able to connect to the destination server. Do you normally use a LAN proxy server to access the web? If so, you will need to configure details of this in Burp at Options > Connections > Upstream proxy servers. There's some more information here: - https://support.portswigger.net/customer/en/portal/articles/2363078-burp-suite-options-upstream-proxy-servers

Burp User | Last updated: Feb 08, 2018 12:31PM UTC

This application is hosted in internal network, in browser it's not loading properly. It is hitting the application but after that just a blank page. but same if I do without burp proxy then it's working fine.

Burp User | Last updated: Feb 08, 2018 12:40PM UTC

The application is not loading properly in browser, then why burp is showing alert "failed to connect". The application is also not using HTTPS

Liam, PortSwigger Agent | Last updated: Feb 08, 2018 01:00PM UTC

When intercept is turned on, Burp Suite should be intercepting the request. The request should appear in the Proxy "Intercept" tab. Are you able to see the http request in this tab? We have two tutorial pages to help you use Burp Proxy within our Support Center, have you checked these out? - https://support.portswigger.net/customer/portal/articles/1783118-getting-started-with-burp-proxy - https://support.portswigger.net/customer/portal/articles/1783119-using-burp-proxy For new users we also recommend that you follow all of our tutorial articles to gain a better understanding of Burp Suite - https://support.portswigger.net/.

Burp User | Last updated: Nov 16, 2018 09:00PM UTC

I had same issue. Burp was able to intercept the requests. Once request was forwarded from Burp there was no response. alerts tab showed "Failed to connect to ......" message. I tried following: Installed certificate in my browser. gave 8080 as Bind to port and selected Loopback only option in Burp Proxy listener Matched this 8080 port in browsers proxy settings. On User options -->Upstream Proxy Servers -->Add--> This opens Add upstream proxy rule window set the following values Destination host = * Proxy host = My corporate proxy(mine had http prefix . I removed it) Proxy port = My corporate proxy port number Authentication type: Basic Username = <domain name>\<my network id> Password = My corporate password I left Domain and Domain host name empty . Clicked OK. This worked for both HTTP and HTTPs request. Hope this helps.

Liam, PortSwigger Agent | Last updated: Nov 19, 2018 08:57AM UTC