Opened 6 weeks ago

Last modified 32 hours ago

#32297 needs_information defect

Version 9 problem (regular and alpha) when some Exit Nodes are blocked by a website firewall

Reported by: mwolfe Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-9.0-issues, tbb-regression, TorBrowserTeam201912
Cc: acat Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In version 8, clicking on the circled i gave a list of the nodes Tor was using, and clicking New Circuit got a new Exit Node, which allowed one to connect to sites that block some (but not all) Tor exit nodes.
With version 9, if unable to connect, clicking the circled i only displays "Connection is not secure", and will not try a different exit node when one clicks on New Circuit, making it much more difficult to connect to sites that block some Tor Exit Nodes.

Child Tickets

Attachments (5)

Screenshot.png (61.5 KB) - added by mwolfe 6 weeks ago.
Screenshot.zip (58.8 KB) - added by mwolfe 6 weeks ago.
screenshot8.0.zip (92.1 KB) - added by mwolfe 6 weeks ago.
screenshot from Tor8.0
SystemInfo.jpg (35.4 KB) - added by mwolfe 5 weeks ago.
TorNotice.zip (22 bytes) - added by mwolfe 5 weeks ago.

Download all attachments as: .zip

Change History (23)

comment:1 Changed 6 weeks ago by gk

Component: - Select a componentApplications/Tor Browser
Owner: set to tbb-team
Status: newneeds_information

Do you have an example where this happens for you? Could you give us a screenshot to see which error message you exactly get and how does the circuit display look like if you click on the (i) icon? Does it show some nodes or nothing or...?

Changed 6 weeks ago by mwolfe

Attachment: Screenshot.png added

Changed 6 weeks ago by mwolfe

Attachment: Screenshot.zip added

comment:2 in reply to:  1 Changed 6 weeks ago by mwolfe

Replying to gk:

Do you have an example where this happens for you? Could you give us a screenshot to see >which error message you exactly get and how does the circuit display look like if you >click on the (i) icon? Does it show some nodes or nothing or...?

Here is the screenshot. As I said, no nodes are shown when Tor cannot connect (because the exit node is blocked by the site dilbert dot com), and clicking the 'New circuit' doesn't seem to do anything the way it did in version 8.

comment:3 Changed 6 weeks ago by gk

Well on your screenshot there is no "New Circuit" button. So, what do you mean? How do you click it in 9.0 in this situation?

How does the error and the circuit display look like with 8.5.5?

Changed 6 weeks ago by mwolfe

Attachment: screenshot8.0.zip added

screenshot from Tor8.0

comment:4 in reply to:  3 Changed 6 weeks ago by mwolfe

Replying to gk:

Well on your screenshot there is no "New Circuit" button. So, what do you mean? How do you click it in 9.0 in this situation?

How does the error and the circuit display look like with 8.5.5?

I can't find the archive of old tor files, but I have the install for Tor7 which updates to Tor8.0 (I used to know the location of all the old Tor files for researchers, but I lost the address.)
Note the screenshot from Tor8.0 when it cannot connect: I get the list of nodes and a New circuit below the list of nodes used.
In Tor9, as you see, I get no nodes. I still have the New Circuit button to the right of the S (for HTTPS Everywhere), or I can use CTRL-SHIFT-L, but it won't create a new circuit. I still get the same Connection is not secure when I click the (s).

comment:5 Changed 5 weeks ago by gk

Cc: acat added
Keywords: tbb-9.0-issues tbb-regression added

The archive for old Tor Browser bundles is at https://archive.torproject.org/tor-package-archive/torbrowser/.

acat: did we miss an error condition here for our circuit display while working on #31562?

comment:6 in reply to:  5 Changed 5 weeks ago by mwolfe

Replying to gk:

The archive for old Tor Browser bundles is at https://archive.torproject.org/tor-package-archive/torbrowser/.

acat: did we miss an error condition here for our circuit display while working on #31562?

Many thanks. I can now check Tor8.5, but figure Tor8.0 shows that the (i) once showed the nodes used when Tor could not connect, but Tor9 does not (and does not allow one to change the circuit to get a different exit node). But it is very useful to be able to access all old versions.

comment:7 Changed 5 weeks ago by acat

Unfortunately I can't reproduce (tested in Linux and Windows with Tor Browser 9). For me the circuit display is working correctly when there is an error, and the "New circuit for this site" button works properly (after *many* new circuits dilbert.com ends up loading).

mwolfe: does it happen only with www.dilbert.com or with any page that has a network error (e.g. can you try with something like www.arandomdomainthatdoesnotexist.com)? Maybe you could you tell us if there are some suspicious errors in Browser Console - Ctrl+Shift+J (ideally with a fresh browser where just www.dilbert.com has been loaded).

Changed 5 weeks ago by mwolfe

Attachment: SystemInfo.jpg added

Changed 5 weeks ago by mwolfe

Attachment: TorNotice.zip added

comment:8 in reply to:  7 Changed 5 weeks ago by mwolfe

Replying to acat:

Unfortunately I can't reproduce (tested in Linux and Windows with Tor Browser 9). For me the circuit display is working correctly when there is an error, and the "New circuit for this site" button works properly (after *many* new circuits dilbert.com ends up loading).

mwolfe: does it happen only with www.dilbert.com or with any page that has a network error (e.g. can you try with something like www.arandomdomainthatdoesnotexist.com)? Maybe you could you tell us if there are some suspicious errors in Browser Console - Ctrl+Shift+J (ideally with a fresh browser where just www.dilbert.com has been loaded).

I have attached the Browser Console messages as TorNotice.zip and SystemInfo.jpg a screenshot of the About page about my Windows. I am running a 2010 computer with a bad graphics chip, so I have to run Windows in Safe Mode so it won't crash (Tor8 works fine, but not Tor9).
I tried www dot arandomepagethatdoesnotexist dot com and got a different error. Dilbert returns 'Problem loading page' and the nonexistent site returns 'Server Not Found' but no nodes and no New Circuit button, just 'Connection Is Not Secure' for both.
The Dilbert problem is basically on all the sites under the gocomics umbrella (they provide cheap sites for several of their major artists who want a personal website, or it might be that the artists asked and were recommended the same ISP that has the same Firewall that blocks some--but not all--Tor exit nodes). I don't have Linux, but I see the same behaviour running OSX Capitan on this computer.

comment:9 Changed 5 weeks ago by sysrqb

Keywords: TorBrowserTeam201911 added

comment:10 in reply to:  7 ; Changed 4 weeks ago by mwolfe

Replying to acat:

Unfortunately I can't reproduce (tested in Linux and Windows with Tor Browser 9). For me the circuit display is working correctly when there is an

mwolfe: does it happen only with www.dilbert.com or with any page that has a network error (e.g. can you try with something like www.arandomdoma

Fixed in latest update. Now I see the New Tor Circuit when I click the (i) after Tor cannot conect! Thanks.

comment:11 in reply to:  10 ; Changed 4 weeks ago by mwolfe

Replying to mwolfe:

Replying to acat:

Unfortunately I can't reproduce (tested in Linux and Windows with Tor Browser 9). For me the circuit display is working correctly when there is an

mwolfe: does it happen only with www.dilbert.com or with any page that has a network error (e.g. can you try with something like www.arandomdoma

Fixed in latest update. Now I see the New Tor Circuit when I click the (i) after Tor cannot conect! Thanks.

Sorry, fixed in OSX Capitan, still not working in Windows 10 ver 1903

comment:12 in reply to:  11 ; Changed 3 weeks ago by gk

Replying to mwolfe:

Replying to mwolfe:

Replying to acat:

Unfortunately I can't reproduce (tested in Linux and Windows with Tor Browser 9). For me the circuit display is working correctly when there is an

mwolfe: does it happen only with www.dilbert.com or with any page that has a network error (e.g. can you try with something like www.arandomdoma

Fixed in latest update. Now I see the New Tor Circuit when I click the (i) after Tor cannot conect! Thanks.

Sorry, fixed in OSX Capitan, still not working in Windows 10 ver 1903

Just to be on the same page here: with 9.0 this was an issue for both macOS and Windows but with 9.0.1 this is no issue any longer for macOS but Windows still remains? If so, can you re-test 9.0 now on your macOS so we can rule out some macOS related software update that fixed this. (old bundles are at: https://archive.torproject.org/tor-package-archive/torbrowser/9.0)

comment:13 in reply to:  12 ; Changed 3 weeks ago by mwolfe

Replying to gk:

Replying to mwolfe:

Fixed in latest update. Now I see the New Tor Circuit when I click the (i) after Tor cannot conect! Thanks.

Sorry, fixed in OSX Capitan, still not working in Windows 10 ver 1903

Just to be on the same page here: with 9.0 this was an issue for both macOS and Windows but with 9.0.1 this is no issue any longer for macOS but Windows still remains? If so, can you re-test 9.0 now on your macOS so we can rule out some macOS related software update that fixed this. (old bundles are at: https://archive.torproject.org/tor-package-archive/torbrowser/9.0)

I am unable to load 9.0 on my Mac. I downloaded it from archive.torproject.org, but when I opened it, when it opened, it announced that it had upgraded itself to 9.0.1.
I tried downloading 8.5, and I was able to stop the upgrade before it finished downloading, but then 8.5 said it wanted to upgrade to 9.0.1, not 9.0

comment:14 Changed 3 weeks ago by acat

So I assume this is now a Windows-only issue. I thought the issue might be reproducible in Windows with safe mode, but unfortunately I could still not reproduce it. It's difficult to track down the problem without more info. Not sure if you TorNotice.zip was intended to be the Browser Console logs that I asked in comment:8, but the file is empty. Could you please check again if there are any errors in Browser Console (Ctrl+Shift+J) when you load the pages with errors and try to request new circuits?

comment:15 in reply to:  13 ; Changed 3 weeks ago by gk

Replying to mwolfe:

Replying to gk:

Replying to mwolfe:

Fixed in latest update. Now I see the New Tor Circuit when I click the (i) after Tor cannot conect! Thanks.

Sorry, fixed in OSX Capitan, still not working in Windows 10 ver 1903

Just to be on the same page here: with 9.0 this was an issue for both macOS and Windows but with 9.0.1 this is no issue any longer for macOS but Windows still remains? If so, can you re-test 9.0 now on your macOS so we can rule out some macOS related software update that fixed this. (old bundles are at: https://archive.torproject.org/tor-package-archive/torbrowser/9.0)

I am unable to load 9.0 on my Mac. I downloaded it from archive.torproject.org, but when I opened it, when it opened, it announced that it had upgraded itself to 9.0.1.

This happens after starting it a second time, yes. But if you just start a fresh version and keep using it you should still have 9.0 because *using* 9.0.1 requires a restart (the update is applied in the background, though).

comment:16 in reply to:  15 ; Changed 2 weeks ago by mwolfe

Replying to gk:

Replying to mwolfe:

Replying to gk:

Replying to mwolfe:

Fixed in latest update. Now I see the New Tor Circuit when I click the (i) after Tor cannot conect! Thanks.

Sorry, fixed in OSX Capitan, still not working in Windows 10 ver 1903

Just to be on the same page here: with 9.0 this was an issue for both macOS and Windows but with 9.0.1 this is no issue any longer for macOS but Windows still remains? If so, can you re-test 9.0 now on your macOS so we can rule out some macOS related software update that fixed this. (old bundles are at: https://archive.torproject.org/tor-package-archive/torbrowser/9.0)

I am unable to load 9.0 on my Mac. I downloaded it from archive.torproject.org, but when I opened it, when it opened, it announced that it had upgraded itself to 9.0.1.

This happens after starting it a second time, yes. But if you just start a fresh version and keep using it you should still have 9.0 because *using* 9.0.1 requires a restart (the update is applied in the background, though).

I vaguely remember I still got the problem with 9.0, but now, as soon as 9.0 starts, it says that 9.0.1 has been added, restart to finish installation, and, with 9.0.1 added (but without a restart) when I try to reach Dilbert and cannot connect, I get the "New Circuit for this Site" button and I can keep clicking until I connect.

I don't know if any changes in 9.0 occur after 9.0.1 is added but no restart, and there doesn't seem to be any way to check. I might have not gotten a 'timed out unable to connect' on OSX Capitan and so didn't notice that 9.0 had the "New Circuit for this Site" since it was not very long from 9.0 until 9.0.1

I first noticed the problem in 9.0a, and it was when 9.0.1 came out, that the 9.xa version also had the "New Circuit for this Site" when it was unable to connect because of a blocked Exit node. I had trouble going back to 8.5 because I installed 9.0a in my Applications folder, and this is NOT a good idea on OSX if one tries to go back and forth between the alpha version and the regular version (I now have both in separate folders on my Desktop).

comment:17 Changed 7 days ago by pili

Keywords: TorBrowserTeam201912 added; TorBrowserTeam201911 removed

Moving tickets to December

comment:18 in reply to:  16 Changed 32 hours ago by mwolfe

Replying to mwolfe:
Finally managed to get a clean copy of Tor 9.0 on OSX10.11.6 El Capitan and no problem of the New Circuit for the Site. Problem is only on my version of Windows, 10 1903.

Note: See TracTickets for help on using tickets.