-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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: unable to reconnect (connection refused. Is the ControlPort Enabled?) 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? Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJWX3RnAAoJEJQqkaGlFNDPiS4H/2g/stKLNl0R1ZzbM2/MmC45 D0t2K8E7mcuIhxDiQJ/klaluJWnTHUrUPonSXTZuMYQJOBjdQIV6Mbq61/2g/TK9 VOdiTIsJSD30wmPIUZXlFb7xGX98DNedsySbCG4evJGmJvmEKXiAwg9i/K0iz5Ar KmRTRxtqCUJcmS+L0s0chV2A7TsIpP2h/WUS/tzc+AmAlbx1jZ4K1zu2uzCqZIjQ 69nkbbHd9DDlmSXvC9aKCB1MO3HcJUgA6gUin4UBOhkrTokbfRQBtizuHqlI4RSG sL9CyOocs9d1DEQVF1pN3PPNjWh/Owm4WzMTm3dMJ+DuRQQ5ls3R+4Fn9I//2Mg= =26fO -----END PGP SIGNATURE-----
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: unable to reconnect (connection refused. Is the ControlPort Enabled?) 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
-----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: unable to reconnect (connection refused. Is the ControlPort Enabled?) 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 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I use debian_tor as my tor group, but I don't think that's the issue. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJWX6pnAAoJEJQqkaGlFNDPMMwH/2j2BcGprDhSpltVoi2w05Ya ZhltimSyg0LmESJaKNLn76ElHk09ZpYbzCfesA1264UhWo+nixGptM2HhSHOUui4 pYV4Yd0XJ7OX6ZpsrJJQnf5s1gWTT72bDagDbomqO25WaNaQWuXvgDqbrMaRbWlS 3oPQ43QRAnyZgcLCx/0YXuv3gd5/XxQ01tMQc3O0Ac3ItN5ol9K5viL1FdNIgqHl QJHYbEAaMpfKnZWyi4zXn/ekBAt+eTzGswLCdY81+3UwTMZwU807M3H5uYdM6zoD H76oaAOx3KOhTX+/L2MySuzvhr60Udv78exTkWbaPz8B1WQxGExjvlEh+SMxClI= =rBwb -----END PGP SIGNATURE-----
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: unable to reconnect (connection refused. Is the ControlPort Enabled?) 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.
-----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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJWX7QPAAoJEJQqkaGlFNDPMo0IAKYdvEgL6fcHcIQrGYC5oc7R D4GefJbOftLC6KmU3kuNn+i5EDB0uFPSkAm2NJWlOjgVRyzAEG3ja95coVLOmyk+ bkWY7sUATr0I9UFWuB8Sh68eg8/SHUinZbso2v+7vK0CuGE2qDDRoq6foxOs3SHv UAzKmjqPMtawYNL0d0f9rbAEflyXNrIS3o/FoKS91js9L3c0voIRvWc/hCWVAYQi PqDmWa99yFyfRcNefLMxq8IOTktY4QmdPy0cQNzO5gskBmTX+y1wYvaRMJQxbEsZ atkuajr3Nhrua2fzQ6rrE3aTCdcsvnEbSPiF6D+u8yeWPNuL75YqGNRaLMT0HX4= =W6f5 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/2/2015 4:54 PM, I wrote:
Doesn't Arm look for 9051?
Robert
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
By default, but it can be any port you edit into the rc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJWX6oXAAoJEJQqkaGlFNDPROoH/RYpXB3sMwhxLsZDQp5Nn3Nz os8WkKC5Xw7mzL7ooDo4EOGDVZmHNKW8IUaVXb6ETdZRtnGlm4I/SR1upmE4mpFJ UwldWwfVCW0khERk08O/MqX0ufIzEH75mmhncs+YcEtzWhjo1mhEISkFC5+3UMXE OLRSg5jcJyLHBkXweqtU1/B9VB3IpP/OgLviq9ItQ2cNHHlD6Ow3YK373Lm9g9Q6 b7gaD8XlxafH8JVlq5YA/JoypRRi5RoXglPKipmeDrgVgriftl5RB/qlCpR0Dbhw SE/PKSjA6U5L7S9WpXjp3y33pl2V5eXRPpBqR7bXXK7dwgeSKZG8X8onXJQFnkA= =rpod -----END PGP SIGNATURE-----
Doesn't Arm look for 9051?
By default, but it can be any port you edit into the rc.
Apologies for the rudimentary question but did you try 'arm --interface 9051'? I assume by 'edit into the rc' that you've changed the default via the armrc but if I was in your shoes I'd give the interface argument a quick try. Also, you can try running 'arm --debug' to possibly get a little more information. Cheers! -Damian
Doesn't Arm look for 9051?
By default, but it can be any port you edit into the rc.
Apologies for the rudimentary question but did you try 'arm --interface 9051'? I assume by 'edit into the rc' that you've changed the default via the armrc but if I was in your shoes I'd give the interface argument a quick try. Also, you can try running 'arm --debug' to possibly get a little more information.
Cheers! -Damian
Baka, typo - meant 'arm --interface 9052' since you're changing away from the default.
On 3 Dec 2015, at 09:44, Kurt Besig <kbesig@socal.rr.com> wrote:
After setting up Tor and tor-arm on the VPS I'm not able to connect with this error: unable to reconnect (connection refused. Is the ControlPort Enabled?) I've edited ~/home/.arm/torrc and /etc/tor/torrc un-commenting the ControlPort 9052 and all the other typical ports, etc..
I don't have enough information to be sure what's going on: What control port is tor actually connected to? (Try "lsof -p <PID>" or "netstat") Can "telnet" or "nc" connect to the port? Does your VPS provider block connections from localhost to localhost by default? (This is an unusual config, that may be why the advice you received didn't help.) What else have your tried?
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?
Possibly. Some VPSs let you modify the firewall settings yourself. Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/3/2015 7:04 PM, Tim Wilson-Brown - teor wrote:
On 3 Dec 2015, at 09:44, Kurt Besig <kbesig@socal.rr.com <mailto:kbesig@socal.rr.com>> wrote:
After setting up Tor and tor-arm on the VPS I'm not able to connect with this error: unable to reconnect (connection refused. Is the ControlPort Enabled?) I've edited ~/home/.arm/torrc and /etc/tor/torrc un-commenting the ControlPort 9052 and all the other typical ports, etc..
I don't have enough information to be sure what's going on:
What control port is tor actually connected to? (Try "lsof -p <PID>" or "netstat")
Can "telnet" or "nc" connect to the port?
Does your VPS provider block connections from localhost to localhost by default? (This is an unusual config, that may be why the advice you received didn't help.)
What else have your tried?
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?
Possibly. Some VPSs let you modify the firewall settings yourself.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B
teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thank you Tim for an intelligent response, I'll look into your suggestions. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJWYQygAAoJEJQqkaGlFNDPHXIIAIFzYAr7AASz9ZE+IRPL2Xbe 2Rh+TOkFEuwzEtE1YlKUuhqKw03zLgwGyBLJ2Qr0QWAofKvuQVDD0xcR7TPKI/th LGMwFKpkmCHj4RnYkHAqwVqczPBShLnCtIrLP1JXgAPwFGl14VGodPRRHBYcw7Oh TNdtgp4Vvx/CL5OyxacoZO4pHIfs4txfx/etYlYd6eYdEJBCm5JxBgJiOLyBdbO9 Se27CW4KqfXy+wxYwz72LUaGyxUnvJ+u6EFAyrZ9KIq1fh/4XDyB6O361hMYl9Na p5INecLGnBIyA3cBZOq28IqZlAu9dNJSlJSU9x7pO0QetVFHpNOte9DVM5A40Mc= =gkcJ -----END PGP SIGNATURE-----
participants (6)
-
Damian Johnson -
fatal -
I -
Kurt Besig -
Michael McConville -
Tim Wilson-Brown - teor