> > Check your firewall, and gateway port forwards if the server is
> > behind a NAT. If you're not sure where to start, post the output of
> > "sudo iptables -L"
> >
> > --Sean
> >
> I've made several iptables and saved them, I thought, however every
> time I reboot the VPS all my rules are
On 12/04/15 00:07, I wrote:
> I thought I was joining a loose but passionate, clever and idealistic
> community.
> I thought I would learn just being a listener and building my knowledge of
> security and servers.
disappointments result from expectations.
i have learned some things by reading
On 12/03/2015 10:09 PM, Michael McConville wrote:
> Kurt Besig wrote:
>> Well. even a doctor would make a few suggestions based on some sort of
>> experience based reasoning. Perhaps some connection problems
>> associated with running tor-arm on a VPS vs. a home server...things of
>> that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/4/2015 8:25 PM, Damian Johnson wrote:
> For what it's worth process permissions aren't at play here. Arm
> is failing to talk with the control port - permissions could cause
> us to be unable to read the authentication cookie, but that would
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/5/2015 3:20 PM, Sean Greenslade wrote:
>>> Dec 05 21:17:46.000 [notice] Your IP address seems to have
>>> changed to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05
>>> 21:17:46.000 [notice] Our IP Address has changed from
>>> 142.4.217.95 to
Just build new torrc, that fixed my issue.
cd /etc/tor/
cp torrc torrc.bak
touch torrc
Use this for torrc (nano torrc), replace some info to match your relay
http://0bin.net/paste/tdUuzTHwZI-BRWQy#JPmufzd+g0W0cx0WyB4g0iU12jU0WFpZRWtKVg6iDbS
When you are done:
sevice tor restart
Then,
sudo
