[tor-relays] Relay down, "rejected", help
jodiemiu at gmail.com
Sat Apr 19 18:04:11 UTC 2014
Enable the ControlPort in your torrc file by uncommenting it, and setup
authentication to the ControlPort in one of two ways: HashedControlPassword
To enable CookieAuthentication, simply remove the hash sign in front of
that line. I can't remember how to do HashedControlPassword off the top of
my head, but can find the answer should you like.
Arm isn't typically run with a config file, but can be with --config-path
if I remember correctly.
On Apr 19, 2014 1:42 PM, "kbesig" <kbesig at socal.rr.com> wrote:
> Getting closer:
> I can run tor arm as root, but get this error as <user>:
> ~$ sudo -u debian-tor arm
> [sudo] password for <user>:
> Connection refused. Is the ControlPort enabled?
> Where is arm's config?
> On 04/19/2014 09:19 AM, kbesig wrote:
>> Sorry for the spam in advance..
>> Install of tor-arm went well enough, no error msg's.
>> ~$ sudo -u debian-tor arm
>> Any ideas??
>> On 04/19/2014 08:16 AM, irregulator at riseup.net wrote:
>>> On 04/19/2014 05:42 PM, kbesig wrote:
>>>> My relay became one of the "rejected" since the heartbleed
>>>> vulnerability surfaced so I reformatted my XP relay and did a fresh Ubuntu
>>>> 14.04 LTS install. Built vidalia-0.2.21 from source using:
>>>> I would suggest completely avoiding (the burden of) Vidalia. You can
>>> just install Tor as standalone daemon :
>>> If you want an interface to inspect your relay's traffic (the reason you
>>> wanted Vidalia?), I suggest tor-arm (provided you've already added Tor's
>>> apt-get install tor-arm
>>> then run :
>>> sudo -u debian-tor arm
>>> tor-relays mailing list
>>> tor-relays at lists.torproject.org
> tor-relays mailing list
> tor-relays at lists.torproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tor-relays