Opened 14 months ago

Closed 4 months ago

#30891 closed defect (invalid) is unreachable commonly, regularly, frequently, persistently, and intermittently

Reported by: monmire Owned by: arlolra
Priority: Medium Milestone:
Component: Applications/Tor Check Version:
Severity: Normal Keywords: Tor Check-unreachable issue
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


This is a common, regular, frequent, persistent, intermittent, and ongoing issue that I first noticed, as I recall, beginning at least 6 or more months ago, frequently driving me to rely on 3rd-party sites to check the IP address of the exit relay.

Attempts to connect to remain stuck commonly, regularly, frequently, persistently, and intermittently at "Performing a TLS handshake to", remaining stuck for up to about 120 seconds, more or less, before the page renders the following message:

"Secure Connection Failed. The connection to was interrupted while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Learn more…Try Again"

At other times, attempts to connect to commonly, regularly, frequently, persistently, and intermittently show the following page message:

"The connection has timed out. The server at is taking too long to respond. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection. If your computer or network is protected by a firewall or proxy, make sure that Tor Browser is permitted to access the Web. Try Again"

At other times, attempts to connect to intermittently will establish a successful, timely, and satisfying connection with Tor Check.

Let's improve the Tor Check connection and configuration so that users will experience a consistently reliable, successful, and timely connection.

Child Tickets

Change History (1)

comment:1 Changed 4 months ago by irl

Resolution: invalid
Status: newclosed

We've completely changed everything since this bug was filed, let's see if another one gets filed in its place, but hopefully this is not an issue anymore.

Note: See TracTickets for help on using tickets.