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

Burp Suite User Forum

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

SUPPORT CENTRE DISCORD

Create new post

This site can't be reached

uzair | Last updated: Dec 10, 2020 08:00AM UTC

I am using ios software version 13.6. i install burp certificate as well. when i open browser and try to search its intially showing some gui then after sometime its shows this error.This site can't be reach.

Uthman, PortSwigger Agent | Last updated: Dec 10, 2020 09:07AM UTC

Can you provide some replication steps, please? You mentioned after "sometime" an error is shown? What error? Is this in your browser? Or in Burp? How long after successfully capturing traffic does this occur? Is the issue affecting all sites? Or only the one you are testing?

uzair | Last updated: Dec 10, 2020 10:47AM UTC

Error occur on both side on browser it shows this site can't be reached and in burp suite it shows 1 the client failed to negotiate a TLS connection to xxxx: Remote host terminated the handshake. "Sometime" ,means it shows UI of any website then after few seconds it shows these error.This happen to all sites.

Uthman, PortSwigger Agent | Last updated: Dec 10, 2020 10:54AM UTC

Which version of Burp are you using?

uzair | Last updated: Dec 10, 2020 12:02PM UTC

I thinks it not version issue because i use professional v2020.11 and i also use community edition also but issue is same

Uthman, PortSwigger Agent | Last updated: Dec 10, 2020 12:24PM UTC

Thanks. Can you try disabling TLSv1.3 on the proxy listener? Select a listener > Edit > TLS Protocols > Use custom protocols > Disable TLSv1.3 > Try accessing the site/application again. If that fails, can you please provide clear replication steps? (details of the site/application too)

cristydavidd | Last updated: Apr 13, 2023 05:57AM UTC

The error message "This site can't be reached" occurs when a user tries to access a website but is unable to connect to the server. There are several reasons why this error message may appear, including problems with resolving the request, the interface application being closed, the database being down, or a dependent service being down. To resolve the issue, users can check the logs for more information on the error, ensure that the application interface, server, and services are running, restart the computer or server and services if needed, confirm that the app is bound to the localhost instead of an individual interface, and run a port scan to ensure that the port is open. https://net-informations.com/q/mis/reached.html

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