You may need to do that yourself here
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Alan
>
> Kindly unsubscribe this email id - "sagard...@gmail.com" from tor mailing
> lists as I am no longer interested in this mailing list. Please do it as
> soon as po
So I moved my Exit node from a Centos install to Debian on the same ip and
copied over the keys to keep things the same.
I've been monitoring the speed and checking things are running properly.
Today as i'm looking at nyx all the flags disappear and replaced with just
the word 'none'.
Did I do so
/common/tortls.o] Error 1
make[1]: Leaving directory `/root/tor-0.3.0.10'
make: *** [all] Error 2
----
I'm running on Centos 7
Alan
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> Hi,
>
> These logs are from a long time after the relay restarted.
> We need to see the logs at the time the relay stops.
>
> Please look at /var/log/tor/log and send us the 20 lines before
> the last message that starts like this:
>
> Tor 0.2.9.10 (git-1f6c8eda0073f464) running on Linux with
> L
>
>> On 22 Jun 2017, at 04:38, Alan wrote:
>>
>>> thanks for running an exit.
>>>
>>>
>>> Alan:
>>>> I've started to see my Exit node restart itself.
>>>
>>>
>>> are you talking about tor daemon /
> thanks for running an exit.
>
>
> Alan:
>> I've started to see my Exit node restart itself.
>
>
> are you talking about tor daemon / process restarts or entire host
> restarts?
>
> I guess you run a RPM based distro.
> I do not think that the
I've started to see my Exit node restart itself.
There is a warning in the log pointing to a problem with OpenSSL but I
don't know how to proceed.
Jun 21 03:07:03.000 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) opening
new log file.
Jun 21 03:07:03.619 [warn] OpenSSL version from headers does not
m and inform them of their error?
Should I just leave it?
Any advice would be very helpful.
Alan.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
38F13E7FEC99D025DB8B89A636EFC1EBC
from torrc on FDB4FC238F13E7FEC99D025DB8B89A636EFC1EBC
MyFamily
$E856ABA2020AA9C483CC2D9B4C878D8D948B0887,$38B330302F1FB79ED11A468FC9DEA8960B842B57
from torrc on 38B330302F1FB79ED11A468FC9DEA8960B842B57
MyFamily
$E856ABA2020AA9C483CC2D9B4C878D8D948B0887
> On Tue, 27 Dec 2016, at 09:59 PM, Alan wrote:
>> # Some problem with dns resulting in [WARN] eventdns: All nameservers
>> have failed - i've switched the dns to 8.8.8.8, only seen that error
>> once
>> since
>
> Please don't use Google's DNS serve
>> From MilkyWay:
>> [root@clutterbuck ~]# ps -p 23780 -o etime
>> ELAPSED
>> 78-14:14:25
>>
>> Hope that helps.
>
> Thanks Alan. All of those are indeed what Stem expects. If you run the
> Nyx codebase instead does the uptime show up? Please note
From Andromeda:
[root@vps110165 ~]# ps -p 972 -o etime
ELAPSED
19-07:43:36
From TheCosmos:
root@Tardis ~ # ps -p 20717 -o etime
ELAPSED
10-06:23:19
Hope that helps.
Alan
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
lta' object has no attribute 'total_seconds'
Alan
> Hey, there's an old python script found many months ago... (attached file)
> If you want to try it, just launch it with command line (I've used a
> linux laptop) :
> ./tshirt.py XXX
>
> XXX is the relay fi
I requested a tshirt but my relays haven't done enough traffic yet. I'll
ask again in a few months.
Alan
> On 2017-01-10 at 20:52, Petrusko wrote:
>> Hi all,
>>
>> This quick mail to inform the tshirt has arrived successfully here !
>>
>> Sooo many th
ate file (21 minutes is missing)"
> The time varies, sometimes it is even negative.
> The operation system is Fedora 25, with arm 1.4.5.0
>
> Greetings,
> Simon Fischer.
>
> On Sun, 2017-01-08 at 10:47 -0800, Damian Johnson wrote:
>> Hi Alan, what linux distribution is
Damian,
Milkyway (which is working) is using Centos 6
Andromeda is using Centos 7
and TheCosmos uses a raspberry pi 2, so Raspbian
> Hi Alan, what linux distribution is this with? The only platform I'm
> aware of having issues with the uptime is OpenBSD. This is because the
> u
I have 3 relays running but on Arm only one shows the uptime. Also the
Averages it keeps are way off.
Alan.___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
that error once
since
# The Consensus Weight was gaining nicely and reached over 7,000 but now
has dive bombed to just 20, with that the speed dropped from ~50mbps to
~5mbps
https://atlas.torproject.org/#details/FDB4FC238F13E7FEC99D025DB8B89A636EFC1EBC
Is this all normal or something i've ov
log when I use
> $ or without a $ sign?
>
> Looking at Atlas the myfamily fingerprints seem to have a $ in front of
> them? But in man pages it just says 'fingerprint' with no syntax
>
> Anyway Atlas can take awhile to update - hours rather than days
>
>
>>
Thanks for that, I've made changes to both torrc files.
I've added MyFamily with each others finger print like so:
MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
Alan
> H
In the UK it depends what ISP your on. Virgin Media gives out static ip's
as far as i know. BT (what i'm using) is dynamic, the ip changes every
time the router reboots. It reboots when it detects a fault which is
normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on h
Thanks for the advice, I added torproject.org repo and it upgraded to 0.2.8.9
Alan
> On Wed, Oct 26, 2016 at 5:54 AM, Peter Palfrader
> wrote:
>> On Wed, 26 Oct 2016, Alan wrote:
>>> 0.2.5.12 is the latest version from the repo. Im assuming I should pull
>>>
0.2.5.12 is the latest version from the repo. Im assuming I should pull
down the source and compile it.
>> Thanks for the update, my main relay was vulnerable but i've patched it
now to 0.2.8.9.
>>
>> My Raspberry Pi is running 0.2.5.12 -- is that ok?
>
> If your version is from before 2016-10-17,
Thanks for the update, my main relay was vulnerable but i've patched it
now to 0.2.8.9.
My Raspberry Pi is running 0.2.5.12 -- is that ok?
> just a reminder since most of the tor network (including some of the
biggest operators) still runs vulnerable relays
>
> https://blog.torproject.org/blog/t
I updated my relay and after installing the update, I pasted my private keypair
in the right file... But in ARM it keeps saying "[WARN] http status 400 ("Looks
like your keypair does not match its older value.”)"
How do I fix this?
Alan
This message contains confidential inf
Steve Snyder:
> On Tuesday, June 23, 2015 9:07pm, saitos...@ymail.com said:
>
>> Besides the obvious requirements of a good relay (e.g. speed, geo-diversity,
>> constant uptime), what qualities make a relay valuable to the Tor network
>> and its
>> users?
>
> A quality that can't be measured:
Hello,
I'm very interested in your endeavor, because SoYouStart is part of OVH,
and they don't really like exit-relays a lot. Please inform us if your
ISP does something against the relay.
Ad security: Make sure you use public-key ssh login and have any kind of
password-login disabled. Try to find
Dear all,
I am currently running a fairly large tor relay (no exit, due to OVH's
restrictive policies) and would like to know if other people have made
experiences with running non-exit relays using OVH's services.
Did any contracts get canceled or did you receive any kind of (legal)
threats by OVH
28 matches
Mail list logo
