On 11/21/2014 09:44 AM, Chuck Peters wrote:
> Nov 16 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:80
> Nov 16 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied
As stated in [1] you could try something like
$> setcap 'cap_net_bind_service=+ep' /usr/bin/tor
[1]
http://s
On 2014-11-21 09:44, Chuck Peters wrote:
Can I work around this issue of after hibernation the node won't bind
to port 80? Or do I need to set it to something above port 1024, for
example the default port 9001?
Yes, but you can redirect traffic from port 80 to 9001 using iptables
and let the
I thought it might be nice to run a relay only node with ORPort 80 because it
might make tor more available to some users where blocking occurs. And to
limit unexpected expenses I calculated 220GB a week would be good. Now I have
found out why running ORPort 80 with AccountingMax is a proble
On 2012-09-11 22:43 , torho...@tor.host-ed.me wrote:
> Hi,
>
> this is my very first post to this list. I operate tor exit relays
> vks24784 and vks24949 and subscribed to Tor Weather Reports. Now, at Sun,
> September 2, 2012 12:17 am and Thu, September 6, 2012 12:33 am, I received
> "Node Down" R
Hi,
this is my very first post to this list. I operate tor exit relays
vks24784 and vks24949 and subscribed to Tor Weather Reports. Now, at Sun,
September 2, 2012 12:17 am and Thu, September 6, 2012 12:33 am, I received
"Node Down" Reports for one of the nodes, 1st report for vks24949, 2nd for
vks
Hi,
this is my very first post to this list. I operate tor exit relays
vks24784 and vks24949 and subscribed to Tor Weather Reports. Now, at Sun,
September 2, 2012 12:17 am and Thu, September 6, 2012 12:33 am, I received
"Node Down" Reports for either of the nodes, 1st report for vks24949, 2nd
for
