Description of problem:
Running tor either as a system service or through vidalia, I cannot reach the tor network in Firefox with proxy settings set by the torbutton plugin.
Steps to Reproduce:
1. Start Tor or Vidalia
2. enable torbutton
3. navigate to https://check.torproject.org/
"Sorry. You are not using Tor."
vidalia log is normal:
[Notice] Tor v0.2.0.35. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
[Notice] Initialized libevent version 1.4.5-stable using method epoll. Good.
[Notice] Opening Socks listener on 127.0.0.1:9050
[Notice] Opening Control listener on 127.0.0.1:9051
[Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Netstat shows vidalia and tor ports open:
tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9051 0.0.0.0:* LISTEN
Version-Release number of selected component (if applicable):
torbutton 1.2.2 (not fedora repo)
System firewall is disabled.
And yet, https://check.torproject.org/ reports I am not using the tor network.
John, do you still have this problem?
I haven't torbutton (but this shouldn't be the problem) and it works for me!
Yes, still having this problem. All components are still at the same version. Any ideas of what to test? As I said, ports are open and torbutton is making the appropriate proxy settings so I'm not sure what else to check. Everything seems fine except browsing isn't going through tor!
$ curl --socks5-hostname localhost:9050 http://www.whatismyip.org/
? Please replace the 'localhost:9050' part with the ip + port accordingly your local installation. When you get a plausible result, you should check firefox + torbutton.
$ curl --socks5-hostname 127.0.0.1:9050 http://www.whatismyip.org
$ curl http://whatismyip.org
I created a new profile in Firefox 3.5.3 and only installed torbutton. It still does not use the proxy and still the test fails. I guess the problem is wholly inside of Firefox/torbutton, then. But I have no idea what it is...
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.