-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/2/2015 7:09 PM, Michael McConville wrote:
Kurt Besig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/2/2015 3:06 PM, Michael McConville wrote:
Kurt Besig wrote:
I just set up a VPS on PulseServers as I noticed quite a few running relays had mostly good things to say about the service. So Far the people operating the servers seem very cooperative and responsive. Anyway I've been running a middle relay for 1.5 years and know the "ropes" pretty well, however a VPS is new to me. After setting up Tor and tor-arm on the VPS I'm not able to connect with this error: I've edited ~/home/.arm/torrc and /etc/tor/torrc un-commenting the ControlPort 9052 and all the other typical ports, etc.. Obviously I'm not able to forward or enable ports on the VPS, so do I need to ask the admin to make some changes?
The arm process needs to be either root's or _tor's (assuming that the tor process uses the _tor user). It's better not to use root, as it's unsafe. So, this will likely work:
sudo -u _tor arm
I use debian_tor as my tor group, but I don't think that's the issue.
Did you try it (sudo -u debian_tor arm)? Worth a shot. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
That's the cmd that leads to: unable to reconnect (connection refused.
Is the ControlPort Enabled?) in tor-arm