The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-09-15T15:33:51Zhttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/68"sign-in from new location" emails contain IP address2020-09-15T15:33:51ZLinus Nordberglinus@torproject.org"sign-in from new location" emails contain IP addressGitLab sends email with the subject "gitlab.torproject.org sign-in from new location" with "A sign-in to your account has been made from the following IP address: <presumably my src IP when accessing gitlab over HTTPS>".
I think this is...GitLab sends email with the subject "gitlab.torproject.org sign-in from new location" with "A sign-in to your account has been made from the following IP address: <presumably my src IP when accessing gitlab over HTTPS>".
I think this is bad behaviour, exposing users IP addresses in (unencrypted) email messages and that Tor Project should stop doing it in order to protect that information in transit and at rest in the users mailbox.
Related, it seems likely that the logic behind this functionality requires users IP addresses to be stored by the GitLab service. This too should be avoided, for better data minimisation.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40650"Signal reload" destroys current tab and spams new tabs2022-07-08T23:46:31Zcypherpunks"Signal reload" destroys current tab and spams new tabsSteps to reproduce:
1. Connect to Tor Browser's Tor's control port (usually 9151), authenticate using a configured authentication method, and send the "signal reload" command. (Usually you'd do this after editing torrc, but that's not r...Steps to reproduce:
1. Connect to Tor Browser's Tor's control port (usually 9151), authenticate using a configured authentication method, and send the "signal reload" command. (Usually you'd do this after editing torrc, but that's not required to reproduce.)
2. In Tor Browser, perform any navigation (click a link, type an address in the URL bar, click a bookmark, etc)
Actual results:
- The current tab is permanently destroyed. By that I mean it is closed and cannot be recovered via Recently Closed Tabs (attempting to do so opens 2 New Tabs instead), there is no way to get the page back using the back button, etc.
- 2 New Tabs are opened.
Expected results: The page navigation works as normal (but with the new Tor config). This was the behaviour up to and including Tor Browser v10.0.x. It broke in v10.5.x, presumably following #27476. Possibly related to #40511
Platform: Windowshttps://gitlab.torproject.org/tpo/core/tor/-/issues/32295"Skipping obsolete configuration option." doesn't say which one2020-06-27T13:49:00ZRoger Dingledine"Skipping obsolete configuration option." doesn't say which oneIn Tor 0.3.5.x:
```
app/config/confparse.c:
log_warn(LD_CONFIG, "Skipping obsolete configuration option '%s'", c->key);
```
But in 0.4.2.3-alpha:
```
lib/confmgt/type_defs.c:
log_warn(LD_GENERAL, "Skipping obsolete configuration option."...In Tor 0.3.5.x:
```
app/config/confparse.c:
log_warn(LD_CONFIG, "Skipping obsolete configuration option '%s'", c->key);
```
But in 0.4.2.3-alpha:
```
lib/confmgt/type_defs.c:
log_warn(LD_GENERAL, "Skipping obsolete configuration option.");
```
Resulting in log messages like:
```
Oct 25 16:19:28.906 [warn] Skipping obsolete configuration option.
Oct 25 16:19:28.906 [warn] Skipping obsolete configuration option.
```
which are not as helpful as they could be.
The bug went in with commit c60a85d2, which I think first went into 0.4.2.1-alpha.
The new file has a XXXX next to this line:
```
// XXXX move this to a higher level, once such a level exists.
log_warn(LD_GENERAL, "Skipping obsolete configuration option.");
```
but I see that most tickets like legacy/trac#29211 and legacy/trac#30866 are scheduled for 0.4.3.x, and this is an 0.4.2 bug so I am filing a separate ticket.
Bug reported by OFFShare in irc.Tor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/42"Snowflake is off. Could not connect to the bridge."2022-07-09T04:32:31ZRoger Dingledine"Snowflake is off. Could not connect to the bridge."I checked my Snowflake proxy in my Firefox, and it told me "Snowflake is off. Could not connect to the bridge." and gave me the option to retry.
I clicked retry, and it connected and seemed happy again.
Was it going to retry on its own...I checked my Snowflake proxy in my Firefox, and it told me "Snowflake is off. Could not connect to the bridge." and gave me the option to retry.
I clicked retry, and it connected and seemed happy again.
Was it going to retry on its own at some point?
This is either a UX bug, "it should tell me it will retry so I don't get anxious that it's broken forever, and maybe the button should be called 'retry now'" or a more serious snowflake bug, "we have a bunch of snowflakes that gave up and we don't know about it". Hopefully the former. :)https://gitlab.torproject.org/tpo/core/tor/-/issues/5373"socksport 2000 testingtornetwork 1" results in socksport 90502020-06-27T14:06:41ZRoger Dingledine"socksport 2000 testingtornetwork 1" results in socksport 9050If you run Tor client with these two options, it ignores your requested socksport.
This is an important bug because it is preventing our Tor network simulators from running the 0.2.3 branch. (Whee.)If you run Tor client with these two options, it ignores your requested socksport.
This is an important bug because it is preventing our Tor network simulators from running the 0.2.3 branch. (Whee.)Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40532"Something Went Wrong" page on connecting to Tor2021-07-14T16:57:05Zcypherpunks"Something Went Wrong" page on connecting to TorI have just downloaded the latest version 10.5
But when I connected to Tor, the page says "Something Went Wrong" and mentions the v2 onion being deprecated and we users need to upgrade to a v3 onion.
I can't find the link where I can u...I have just downloaded the latest version 10.5
But when I connected to Tor, the page says "Something Went Wrong" and mentions the v2 onion being deprecated and we users need to upgrade to a v3 onion.
I can't find the link where I can upgrade to v3 onion. How do non-tech users upgrade to this v3 onion?https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11014"Start Tor Browser.exe" from another directory fails to start Tor Launcher, g...2020-06-27T14:42:17ZDavid Fifielddcf@torproject.org"Start Tor Browser.exe" from another directory fails to start Tor Launcher, gives Mozilla brandingIf you run Start Tor Browser.exe from the command line from other than the directory it's in, Tor Launcher doesn't run and you get the normal Firefox branding. If you try to browse anywhere, you get "The proxy server is refusing connecti...If you run Start Tor Browser.exe from the command line from other than the directory it's in, Tor Launcher doesn't run and you get the normal Firefox branding. If you try to browse anywhere, you get "The proxy server is refusing connections".Erinn ClarkErinn Clarkhttps://gitlab.torproject.org/tpo/core/arti/-/issues/302"static" feature turns on native-tls even when it isn't wanted2022-04-07T15:54:25ZNick Mathewson"static" feature turns on native-tls even when it isn't wantedThe "static" trait in tor-rtcompat turns on `native-tls/vendored`.
That was fine before we added `rustls` support, but now it's wrong: it will make us turn on `native-tls` even if we didn't want it.
We should resolve this somehow; it m...The "static" trait in tor-rtcompat turns on `native-tls/vendored`.
That was fine before we added `rustls` support, but now it's wrong: it will make us turn on `native-tls` even if we didn't want it.
We should resolve this somehow; it may also require a solution at the level of the `arti` and `arti-client` crates.Arti 0.1.0 release: Okay for experimental embeddingNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/web/donate-static/-/issues/126"Stripe webhook recovered"2023-09-28T14:56:32Zal smith"Stripe webhook recovered"Hi,
We received an email to accounting@tpo:
![Screenshot 2023-09-27 at 4.42.45 PM.png](/uploads/8ec3b0653b68185e6add035bb8c12a32/Screenshot_2023-09-27_at_4.42.45_PM.png){width=461 height=405}
Not sure what it means. Can someone check ...Hi,
We received an email to accounting@tpo:
![Screenshot 2023-09-27 at 4.42.45 PM.png](/uploads/8ec3b0653b68185e6add035bb8c12a32/Screenshot_2023-09-27_at_4.42.45_PM.png){width=461 height=405}
Not sure what it means. Can someone check on this?https://gitlab.torproject.org/tpo/core/tor/-/issues/18024"sum" accounting displays bad log message2020-06-27T13:59:48ZNick Mathewson"sum" accounting displays bad log messageWhile doing an implementation for legacy/trac#15989, unixninja fixed this issue. Giving it a bug number for the changelog.While doing an implementation for legacy/trac#15989, unixninja fixed this issue. Giving it a bug number for the changelog.Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/tpo/community/support/-/issues/40002"support wiki" is going away2020-06-24T21:18:04Zanarcat"support wiki" is going awayHi!
I am not sure anyone here is aware of it, but there's a wiki for the community/support team!
https://help.torproject.org/support/
This was managed by Lunar and hasn't been updated in about 6 years, so I doubt anyone still uses it....Hi!
I am not sure anyone here is aware of it, but there's a wiki for the community/support team!
https://help.torproject.org/support/
This was managed by Lunar and hasn't been updated in about 6 years, so I doubt anyone still uses it. Since we migrated the TPA wiki (help.tpo) to gitlab (tpo/tpa/services#34437), we figured we would cleanup a few things and have simply removed that page from the new wiki:
https://gitlab.torproject.org/tpo/tpa/services/-/wikis/home
The help.tpo site will survive, as a redirect, however. I propose to redirect to support.torproject.org, since it's where support is organized nowadays.
Makes sense?https://gitlab.torproject.org/tpo/core/tor/-/issues/25136"system clock jump" warnings still persist2020-06-27T13:54:14ZTrac"system clock jump" warnings still persistThis is an addition to legacy/trac#25052 as it was directly closed before I could reply.
I have changed my relay settings as recommended and disabled the "DirCache", set an "Address" and removed the (in any case temporary) cpu pinning. ...This is an addition to legacy/trac#25052 as it was directly closed before I could reply.
I have changed my relay settings as recommended and disabled the "DirCache", set an "Address" and removed the (in any case temporary) cpu pinning. At least it helped to reduce the "jump clock" warnings to one every one or two hours. But they are not gone.
```
Feb 2 06:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 1 day 11:27 hours, with 0 circuits open. I've sent 13.59 MB and received 26.91 MB.
Feb 2 06:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Feb 2 06:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 20 v4 connections; and received 11 v1 connections, 22 v2 connections, 0 v3 connections, and 131 v4 connections.
Feb 2 12:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 1 day 17:27 hours, with 0 circuits open. I've sent 13.59 MB and received 26.91 MB.
Feb 2 12:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Feb 2 12:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 20 v4 connections; and received 11 v1 connections, 22 v2 connections, 0 v3 connections, and 131 v4 connections.
Feb 2 12:11:51 <daemon.notice> Tor[1941]: Your IP address seems to have changed to 178.1.226.79 (METHOD=RESOLVED HOSTNAME=bundesgebaermutter.ddnss.eu). Updating.
Feb 2 12:11:51 <daemon.notice> Tor[1941]: Our IP Address has changed from 178.1.228.74 to 178.1.226.79; rebuilding descriptor (source: METHOD=RESOLVED HOSTNAME=bundesgebaermutter.ddnss.eu).
Feb 2 12:11:57 <daemon.notice> Tor[1941]: Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Feb 2 12:11:58 <daemon.notice> Tor[1941]: Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 2 12:11:58 <daemon.notice> Tor[1941]: Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 2 12:11:58 <daemon.notice> Tor[1941]: Performing bandwidth self-test...done.
Feb 2 14:01:39 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb 2 18:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 5:54 hours, with 0 circuits open. I've sent 15.22 MB and received 29.82 MB.
Feb 2 18:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 9/9 NTor.
Feb 2 18:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 23 v4 connections; and received 11 v1 connections, 25 v2 connections, 0 v3 connections, and 151 v4 connections.
Feb 2 18:44:21 <daemon.warning> Tor[1941]: Your system clock just jumped 1720 seconds forward; assuming established circuits no longer work.
Feb 2 18:47:08 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 2 20:29:55 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 2 21:49:42 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 2 22:56:29 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 00:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 11:18 hours, with 1 circuits open. I've sent 17.56 MB and received 32.43 MB.
Feb 3 00:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 2/2 NTor.
Feb 3 00:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 25 v4 connections; and received 12 v1 connections, 32 v2 connections, 0 v3 connections, and 174 v4 connections.
Feb 3 02:05:15 <daemon.warning> Tor[1941]: Your system clock just jumped 106 seconds forward; assuming established circuits no longer work.
Feb 3 05:19:02 <daemon.warning> Tor[1941]: Your system clock just jumped 105 seconds forward; assuming established circuits no longer work.
Feb 3 06:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 17:15 hours, with 1 circuits open. I've sent 18.47 MB and received 34.66 MB.
Feb 3 06:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 1/1 NTor.
Feb 3 06:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 25 v4 connections; and received 12 v1 connections, 39 v2 connections, 0 v3 connections, and 198 v4 connections.
Feb 3 09:19:20 <daemon.warning> Tor[1941]: Didn't recognize cell, but circ stops here! Closing circ.
Feb 3 09:19:20 <daemon.warning> Tor[1941]: circuit_receive_relay_cell (forward) failed. Closing.
Feb 3 10:38:48 <daemon.warning> Tor[1941]: Your system clock just jumped 105 seconds forward; assuming established circuits no longer work.
Feb 3 12:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 23:13 hours, with 2 circuits open. I've sent 19.70 MB and received 36.97 MB.
Feb 3 12:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 1/1 TAP, 1/1 NTor.
Feb 3 12:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 26 v4 connections; and received 13 v1 connections, 43 v2 connections, 0 v3 connections, and 221 v4 connections.
Feb 3 12:31:37 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 14:43:25 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb 3 16:12:13 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb 3 17:08:00 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 18:09:47 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 18:09:47 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 1 day 5:06 hours, with 2 circuits open. I've sent 23.34 MB and received 41.04 MB.
Feb 3 18:09:47 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 1/1 NTor.
Feb 3 18:09:47 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 35 v4 connections; and received 13 v1 connections, 47 v2 connections, 0 v3 connections, and 264 v4 connections.
Feb 3 19:49:35 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 21:31:23 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
```
The "address-hostname" is resolved by a dynamic dns provider in germany (bundesgebaermutter.ddnss.eu) and Atlas/Metrics shows the fqdn of my dial-up connection (xxxx.vodafone-ip.de). And tor is causing only little spikes in the cpu usage graph now. When the consensus diffs were computed it took half an hour or more at 100 percent on the poor bPi SoC.
Granted, it is a low-volume relay. Maybe I should just shut up ;)
**Trac**:
**Username**: bundesgebaermutterTor: unspecifiedhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41057"Take Screenshot" doesn't work2022-07-17T16:07:53Zdeeplow"Take Screenshot" doesn't work<!--
* Use this issue template for reporting a new bug.
-->
### Summary
**Summarize the bug encountered concisely.**
When on a page, if we right-click, there is an option to take a screenshot just like firefox, but it does nothing.
###...<!--
* Use this issue template for reporting a new bug.
-->
### Summary
**Summarize the bug encountered concisely.**
When on a page, if we right-click, there is an option to take a screenshot just like firefox, but it does nothing.
### Steps to reproduce:
**How one can reproduce the issue - this is very important.**
1. right-click on page
2. click on "take screenshot"
### What is the current bug behavior?
Nothing happens when you click the button
### What is the expected behavior?
Take a screenshot just like in firefox
### Environment
**Which operating system are you using? For example: Debian GNU/Linux 10.1, Windows 10, Ubuntu Xenial, FreeBSD 12.2, etc.**
**Which installation method did you use? Distribution package (apt, pkg, homebrew), from source tarball, from Git, etc.**
Qubes, Whonix, 11.0.15 (based on Mozilla Firefox 91.10.0esr) (64-bit)
### Relevant logs and/or screenshots
![take_screenshot](/uploads/f24aa7c9d455b37adaacb2c893e3e7b1/take_screenshot.png)https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/24126"Temporarily allow all this page" breaks JS on all already opened HTTPS sites...2022-06-23T02:07:32Zcypherpunks"Temporarily allow all this page" breaks JS on all already opened HTTPS sites (on Medium Security)NoScript has issues again with enabling JS, see legacy/trac#23747.
This is with NoScript 5.1.4.NoScript has issues again with enabling JS, see legacy/trac#23747.
This is with NoScript 5.1.4.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/23747"Temporarily allow all this page" breaks JS on all other tabs2020-06-27T14:36:51Zcypherpunks"Temporarily allow all this page" breaks JS on all other tabssubjsubjhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/24421"Temporarily allow all this page" get inherited when New Identity is chosen.2020-06-27T14:36:38Zcypherpunks"Temporarily allow all this page" get inherited when New Identity is chosen.How to reproduce:
1. Open Tor Browser.
2. Select "High" Security Setting.
3. Go to https://github.com/
4. Click on NoScript icon and choose "Temporarilly allow all this page".
5. You can note that when the page gets refreshed the canvas...How to reproduce:
1. Open Tor Browser.
2. Select "High" Security Setting.
3. Go to https://github.com/
4. Click on NoScript icon and choose "Temporarilly allow all this page".
5. You can note that when the page gets refreshed the canvas prompt is displayed.
6. Select New Identity in the Torbutton.
7. Go to https://github.com/
8. You can notice that the canvas prompt is displayed (meaning JS is enabled, which in turn implies that "Temporarilly allow all this page" gets inherited when New Identity is chosen.)https://gitlab.torproject.org/tpo/core/tor/-/issues/4094"TestSocks 1" and IP addresses in requests using "safe" socks protocols resul...2020-06-27T14:07:42Zfk"TestSocks 1" and IP addresses in requests using "safe" socks protocols result in misleading log messagesAccording to the man page, the TestSocks option causes Tor to
"make a notice-level log entry for each connection to the Socks
port indicating whether the request used a safe socks protocol
or an unsafe one".
In case of "safe" socks prot...According to the man page, the TestSocks option causes Tor to
"make a notice-level log entry for each connection to the Socks
port indicating whether the request used a safe socks protocol
or an unsafe one".
In case of "safe" socks protocols Tor however goes a bit
further and always claims:
Your application (using socks(4a|5) to port 80) gave Tor a hostname, which means Tor will do the DNS resolve for you. This is good.
The message is printed even if the application actually gave
Tor an IP address and not a hostname.
I think Tor should either verify that a hostname has been given,
or the log message should be reworded to something like:
Your application (using socks(4a|5) to port 80) instructed Tor
to take care of the DNS resolution itself if necessary. This is good.https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/25926"The anonymous Internet" page on metrics has malicious looking links2020-06-27T14:25:54Zpastly"The anonymous Internet" page on metrics has malicious looking linksAs abrasively reported on [Reddit](https://redd.it/8f1tml) ...
It appears geography.oii.ox.ac.uk no longer is a link worth clicking on. In fact, it might be actively malicious now.As abrasively reported on [Reddit](https://redd.it/8f1tml) ...
It appears geography.oii.ox.ac.uk no longer is a link worth clicking on. In fact, it might be actively malicious now.https://gitlab.torproject.org/tpo/core/tor/-/issues/162"The service did not return an error." message2020-06-27T14:11:07ZTrac"The service did not return an error." messageGet "The service did not return an error." message when trying to stop service in services.msc in windows (on windows XP SP2). It does close the process, and if you try and tell it to stop again, it just hangs for a while, and eventually...Get "The service did not return an error." message when trying to stop service in services.msc in windows (on windows XP SP2). It does close the process, and if you try and tell it to stop again, it just hangs for a while, and eventually says that it stopped. After this you can hit start process, and everything works normally.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: bknobbshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/23241"This page isn't redirecting properly" errors in TorBrowser but not in Firefox2020-06-27T14:37:06ZTrac"This page isn't redirecting properly" errors in TorBrowser but not in FirefoxThe subject error appears on many URLs with TorBrowser. The few that I have tried in regular Firefox work fine. One such example is http://www.jreast.co.jp/en. The problem also happens when tumblr redirects the browser to unmasked "sensi...The subject error appears on many URLs with TorBrowser. The few that I have tried in regular Firefox work fine. One such example is http://www.jreast.co.jp/en. The problem also happens when tumblr redirects the browser to unmasked "sensitive" blogs.
None of the reasons given in Firefox's help for this error seems to apply to TorBrowser: cookies are enabled, network.http.sendReferer is enabled, etc.
I am using TB 7.0.4.
**Trac**:
**Username**: msfc