Tor Browser 7.0.6 is released

Tor Browser 7.0.6 is now available from the Tor Browser Project page and also from our distribution directory.

[UPDATE: the dist server was temporarily messed up, but it should be better now. Sorry for the troubles!]

This release features important security updates to Firefox.

This release includes security updates for Firefox (52.4.0esr) and a new Tor stable version (, the first one in the 0.3.1 series. In addition to that we updated the HTTPS Everywhere and NoScript extensions we ship. Moreover, we fixed minor usability issues and a bug which, under particular circumstances, caused all tabs to crash after closing single one.

Note: The release date in the changelog displayed after the update is incorrect. The actual release date is September 28.

The full changelog since Tor Browser 7.0.5 is:

  • All Platforms
    • Update Firefox to 52.4.0esr
    • Update Tor to
    • Update Torbutton to
      • Bug 22542: Security Settings window too small on macOS 10.12 (fixup)
      • Bug 20375: Warn users after entering fullscreen mode
    • Update HTTPS-Everywhere to 2017.9.12
    • Update NoScript to 5.0.10
    • Bug 21830: Copying large text from web console leaks to /tmp
    • Bug 23393: Don't crash all tabs when closing one tab
  • OS X
    • Bug 23404: Add missing Noto Sans Buginese font to the macOS whitelist

Could you upload a screenshot for the bottom/top issue? I am not sure whether I am understanding you correctly.

Regarding the frame issue: is it a problem in a freshly downloaded Tor Browser as well? If so, how do you configure your NoScript?

October 03, 2017


I can no longer play video using my tor browser. I recently upgraded to MAC high sierra. I am unable to uninstall high sierra. What do I need to do to fix?

October 03, 2017



1) In 99% of the cases my 1st proxy in the Tor circuit comes from Germany. Is there a way to forbid Tor to connect to any proxy in Germany (or to any other country)?

2) Once Tor has connected to a page, the 1st proxy never changes. Even if I request a new identity the 1st proxy stays, thus I have no other choice but to delete and reinstall Tor and hope that by the next installation it does change.


October 05, 2017


When I used one baggy HS I sometimes do NEWNYM and kill -1 for tor. Once I noticed this:

Oct 05 XX:19:18.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Oct 05 XX:19:42.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.
Oct 05 XX:19:42.000 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Oct 05 XX:19:42.000 [notice] Read configuration file "/etc/tor/torrc".
Oct 05 XX:19:42.000 [notice] Tor (git-5fa14939bca67c23) opening log file.
Oct 05 XX:19:43.000 [warn] connection_ap_attach_pending(): Bug: 0xXXXXXXXXXXXX is no longer in circuit_wait. Its current state is waiting for rendezvous desc. Why is it on pending_entry_connections? (on Tor )
Oct 05 XX:21:43.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)

Do I have something to worry about? Is is safe to report that XXXXXXXXXXXX which follows "Bug" word? Is it related to ? I can speculate that HS is extensively used, DDoSed and some HSDirs may censor its descriptor. All that results in unreliable connection.

Thanks, I reopened the bug in our bug tracker pointing to your comment. Yes, I think reporting the XXXXXXXXXXXX in that case is safe as well.

OK, then I can disclose that it was:

Bug: 0x564a96ed6ff0 is no longer in circuit_wait.

Thanks for reopening that ticket. I don't know Tor protocol well, but could speculate that tor client requests HS descriptor from time to time. If HS is intensively used during those requests, due to time lag it may happen that old descriptor cannot be used, but new one is not prepared yet. I remember that sometimes I also experienced another error with this HS:

[warn] Query '[scrubbed]' didn't have valid rend desc in cache. Failing.

These problems may be related. Anyway, does it harm my anonymity? Is it just technical internal error not related to deanonymization of HS clients?

I have used the Tor Browser under Suse Linux for more than one year - until now it was never a problem to update Tor upon the messages to do so (I use version 7.0.5 currently). Yet the update to 7.0.6 does not work, though I tried to update more than 10 times in the meantime. Could you please suggest a solution? - Thx.

What does "not work" mean? Does it not download? Does the update not apply properly? Could you open about:config in your Tor Browser and set app.update.log to true. Make sure to restart and then open the browser console with Ctrl+Shift+J you should now see the update log in case an update is tried. You can trigger that by clicking on the hamburger menu in the upper right corner and selecting "?" and "About Tor Browser". Does the log give some hint on what is going wrong?

This problem happened, 2 days after updating
1- NoScript icon change position
2- NoScript>>>Options>>>Embeddings>>> I had in Forbid, are now Enabled!


I reinstalled the Torbrowser, and now I have no problems, but I want to know, that was what happened, this had never happened before with my browser

Someone hack me or is a problem with the update?

I appreciate the opportunity to express my problem
I hope an answer, Thank you!

I think this was due to a buggy NoScript update which hopefully will be fixed before another such an update is happening. We track this in "Just" restarting the browser should have fixed the problem as well.

FYI, Tor circuit viewer on Tor Browser was broken (didn't show up) for years on my Windows 7, but after I believe updating tor.exe to it now started showing up again. Could you confirm? I haven't seen anything in the changelogs of Tor and Tor Browser relating to this issue

We did not fix anything in that regard. But glad that it is working for you again!

07.10.2017 7:48:34.800 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
07.10.2017 7:50:10.600 [WARN] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Connection refused [WSAECONNREFUSED ]; CONNECTREFUSED; count 10; recommendation warn; host 7BF46AD9A0F7F7CFC5CC131417E71DF1A516368F at
07.10.2017 7:50:10.600 [WARN] 9 connections have failed:
07.10.2017 7:50:10.600 [WARN] 8 connections died in state handshaking (TLS) with SSL state SSLv3 read finished A in HANDSHAKE
07.10.2017 7:50:10.600 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
07.10.2017 7:50:32.800 [NOTICE] Closing no-longer-configured Socks listener on
07.10.2017 7:50:32.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
07.10.2017 7:50:32.800 [NOTICE] Closing old Socks listener on
07.10.2017 7:50:32.800 [WARN] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 11; recommendation warn; host B6904ADD4C0D10CDA7179E051962350A69A63243 at
07.10.2017 7:50:32.800 [WARN] 11 connections have failed:
07.10.2017 7:50:32.800 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv3 read finished A in HANDSHAKE
07.10.2017 7:50:32.800 [WARN] 2 connections died in state connect()ing with SSL state (No SSL object)
07.10.2017 7:50:39.500 [WARN] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 12; recommendation warn; host 4CE25D32F42026361317F069A2E49F300DD56DA6 at
07.10.2017 7:50:39.500 [WARN] 12 connections have failed:
07.10.2017 7:50:39.500 [WARN] 10 connections died in state handshaking (TLS) with SSL state SSLv3 read finished A in HANDSHAKE
07.10.2017 7:50:39.500 [WARN] 2 connections died in state connect()ing with SSL state (No SSL object)
07.10.2017 7:50:39.500 [WARN] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 13; recommendation warn; host E2382981C6D5876D26237FEACED9DBE324724194 at
07.10.2017 7:50:39.500 [WARN] 14 connections have failed:
07.10.2017 7:50:39.500 [WARN] 11 connections died in state handshaking (TLS) with SSL state SSLv3 read finished A in HANDSHAKE
07.10.2017 7:50:39.500 [WARN] 3 connections died in state connect()ing with SSL state (No SSL object)
07.10.2017 7:50:39.500 [NOTICE] Delaying directory fetches: DisableNetwork is set.

It seems your network connection gets censored. You could try to use bridges to work around that. If you download Tor Browser and start it for the first time you could choose the "Configure" option and select to use bridges. See: for a guide. Let us know if that works for you.

hey when are you going to fix this stupid shit. Every time I exit I get a message from Windows 8 "Tor Browser has stopped working". This has been going on since last 2 updates.

That is So far it is hard to reproduce the bug for us. But the good news is that I'll have a machine available in about two weeks where I think the bug is occurring. I'll look at it then.

After normal TBB shutdown (clicking upper right corner "X"), I have seen Windows crash error in Vista before Microsoft's April EOL, and in Windows 7 since switching to Windows 7.…
(off-topic comment: to reduce "clues" sent out about TBB use, I always choose the second choice "Close the program".)

Maybe the TBB profile has accumulated "cruft"?
My profile had been the same for years on Vista.
I had copied my profile from Vista to the fresh Windows 7 installation.
Exception: Firefox allows no good way to export places.sqlite to .url files ("favorites"), so I very recently set aside my accumulated huge places.sqlite, and let TBB's next startup generate a new places.sqlite. I deleted Mozilla's default bookmarks and have added only about 11.

Other non-standard settings:
Accumulated about:config prefs, and some that may be obsolete.
Noscript settings
Other than places.sqlite, some .sqlite files data, such as form history?
Few words added to Spelling dictionary.
Rare https cert exceptions.

I intend to download the current full TBB.
Run it once. I doubt it will crash at shutdown.
Then try some diff type comparison of this new TBB profile against my accumulated profile.
Gradually I will research the differences, and "rebuild" the new profile.

I've looked all over the place and can't seem to find a link to which versions of OSX are now supported (I'm now getting 'your browser is out-of-date but the latest version is not supported on your system. upgrade your OS' messages, but my machine is AT the max OS it can handle).

Can anybody point me to the link; if there IS one? Tnx.

We are following the required versions for Firefox. Currently that means Tor Browser is supporting all macOS versions starting with 10.9.

  1. [warn] Tried connecting to router at X.X.X.X:9001, but RSA identity key was not as expected: wanted XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + no ed25519 key but got XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.<br />

Is it some bug in tor code or is it just node with bug? (

Ich möchte den Tor Browser gerne nutzen

Just download it down from our website for your particular platform and extract/start it:

Ever since upgrading from 7.0.3 to 7.0.4 the warning for maximizing Tor disappeared.Upgrading to 7.0.5 did not fix the problem for me and the latest 7.0.6 did not fix it either.Of course I know that the page should not be maximized , but there are occasions that some trusted person uses my machine and they don't see the warning when maximizing the page and keep using it at that size until I see it and tell them.I use Windows 7 Ultimate , 64-bit.
I use Kaspersky Internet Security Suit and I wonder if that might have some tricks to do stop the warning . Last year , I was using Bitdefender and I always got the warning.I write from Iran.

You only should get it three times then Tor Browser assumes it has nagged you enough and is stopping to do so.

First issue:top / bottom problem:

Sorry for not having reacted so far – too much work and I had to try out several combinations of setting on different sites.

So I'll have another try to explain the point I'm aiming at:

1. load the following page:…

2. change security slider:

a) low > you will see the top of the page
b) middle > you will see the bottom of the page
c) high > you will see the bottom of the page

3. Why is the bottom of the page displayed with the security slider on middle and high?

4. Can't this behaviour be changed in general so that the top of such pages will always be displayed? Since you get the “clickomania” and “scrollomania” on sites with search fields on sites of dictionaries like “” where you maybe have 50 words to look up.

Thanks for checking!

Second issue: icon problem:no noscript icon on iframes is missing

1. load the following page:…

2. check if all settings are in the original state (security slider and noscript)

3. change settings in noscript:

a) click on click on “Embeddings”
b) check “forbid iframes”
c) click on “OK”

4. reload the above page

5. effect:

a) iframe is forbidden = yellowish frame – that is correct


The noscript icon is missing! It should be displayed on the left upper corner of the frame, shouldn't it?

The noscript icon is missing only in the tor browser. In the regular firefox with the regular noscript installed, the noscript icon is displayed on the left upper corner of the frame.

I hope I've put it more understandable and the effect of the missing noscript icon is reproducible now.

I'd be grateful if you could check if that is a normal behaviour …

Thanks a lot!

Yes, next week.

"FIREFOX browsers will soon block "fake news" flagged by George Soros-linked left-wing groups"

It's that true?………

I dont need modzilla or any other to tell me what is"truth and facts", that's not democracy


Thank you for your good work with Tor and Tor browser, but with the latest release I have some crash with the extensions control tab, with previous release nothing. My system is Windows 7 Ultimate 32 bit.

Could you give us some steps to reproduce your problem? How exactly can I trigger it?

To explain in detail my problem to show when I open the extensions list tab and, for example, switching to plugin list tab and return to extensions list tab tor browser is very slow and crash, therefore I to reboot the application. This problem not show always but very often; It is very bother. I hope us to fix it because with old versions I not had any problem. Thank you.

Do you have any plugins listed in the plugins tab? I assume this happens on Windows?

No, I not have any plugins listed in the plugins tab and the extensions are the default bundled in Tor browser. The problem is like the application does not load correctly the extensions tab and crash all application. I will test new Tor browser versions to this problem and I'll let you know. System is Windows 7 Ultimate 32 bit.

Have no title on the of Browser window for the

Which operating system are you on? Which Tor Browser bundle locale are you using? Could you make a screenshot showing your problem?

nice job guys

Today's Tor for Mac v 7.0.7 update appeared on MacUpdate, yet the latest version on the TOR site is still 7.0.6. The new one does download if you replace the version numbers in the link, but when 7.0.7 runs it reports TOR is out of date, and checking for updates returns no update available. Bizarre.

From the comments on MacUpdate it seems this happened with 7.0.6 as well. What gives?

I guess MacUpdate is releasing 7.0.7 earlier than we for some reason. There is not much we can do about that.

browser its nice application

dear tor team
how can i say thanks when i living in dictatorship.
god bless you

rspctd gk.

i m at 8.0a2 beta on win 64 sys last few hrs getting in known w Tor. Thanks!

still reading all the docs for d sake of my surf and Tor as well

wud u b so kind to hint me on html5 audio enabling for I dont wanna poisonn Tor w any jscript? pls.

afterwards, i d ask you on how to begin on w. bridge networking.. i v got bridge keys, still cant make an input in config.

d love to do any for the \

thnnx in advnc.

Tor rebooted sev times still no audio (html5)

err " Your browser does not seem to support HTML5 WebAudio; please try a recent version of Firefox, Chrome, Opera or Safari; or switch to Java."

bsht lol