tor-relays

tor-relays@lists.torproject.org

42 participants
4821 discussions

Guard flag got removed after only 48 hours of downtime.
by William Kane 11 Aug '20

11 Aug '20

Please discard the previous (empty) email, it was an error on my end. Today, I noticed that my guard flag has been taken away: https://metrics.torproject.org/rs.html#details/47E1157F7DA6DF80EC00D745D73A… Does this have to do with the recent two, major downtime's of the relay? While I wasn't monitoring the server, the kernel decided (or rather oom-killer did) to reap the tor process for consuming too much memory (keep in mind, this is a virtual machine with only 1GB of RAM which running another daemon consuming about ~92MB's of RAM). I promptly restarted the relay, but the same thing happened again yesterday. So today, I manually set a lower MaxMemInQueues value instead of letting Tor calculate one for me - 640MB's instead of 732MB's. Still, I am confused as for why the guard flag has been taken away - I recently opted in to be a fallback directory mirror, does this have anything to do with it? The relay was stable and online for almost a year, so only 48 hours of downtime shouldn't affect the variables qualifying a relay to become and stay a guard that much? If this is because of the directory mirror thing, then please take my relay out of that pool - I want to stay a guard for a number of reasons - mainly because my host is only hosting about 10 tor relays unlike all the other big hosters that are commonly used - network variety is very important or so I've been taught, especially when it comes to guard relays. If this is a mistake on Tor Project's end, I please ask for it to be resolved - however, if it's the Directory Authorities disqualifying my relay, then there's nothing to be done except to wait. Greetings, William Kane

5 11

why non-exit node becomes last in the circuits?
by tor-operator-sahara-it 10 Aug '20

10 Aug '20

Hello. On Tails: Today i found that my jabber messenger (with server in *.onion) use onion circuit with three nodes, and two times from two exit-nodes were very strange. https://metrics.torproject.org/rs.html#details/92E807AC5E23CCD9FE623EA4DC02… https://metrics.torproject.org/rs.html#details/AC5CECEF6AF649F2A7F047D102FE… They havnt exit-flag. Why it happen?

3 3

This would be better in bold, methinks - IPv6 troubleshooting
by torix＠protonmail.com 10 Aug '20

10 Aug '20

An important piece of mental furniture that I never needed to know until months later when a relay stopped working is right here in Step 7: Check IPv6 Availability of page https://community.torproject.org/relay/setup/post-install/ "If you enable IPv6 without working IPv6 connectivity your entire relay will not be used, regardless if IPv4 is working." This seems to me to be quite idiosyncratic to tor, and easily forgotten - not the first thing I would think about when troubleshooting, nor is the post-install page quite where I would look for help when a relay stopped. As we move more and more to including IPv6 in our relay setups, this will come up more often. But we should at least add bold here. --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Relay dropped all traffic
by Sebastian Elisa Pfeifer 08 Aug '20

08 Aug '20

Hey, so one of my relays [0] dropped all traffic. Tor Metrics says its down for 4 days now, but "last restarted" correctly states today at 19:06. Also, on the metrics page is has the flags Fast, Guard, Running, Stable, V2Dir, Valid and ReachableIPv6, but when I SSH into it and look in nyx, it says there "flags: none". I tried rebooting multiple times. The Log tells me "Aug 07 02:36:12.000 [notice] Heardbeat: It seems like we are not in the cached consensus." I have attached the log with the events since the last restart today at 19:06 Should I just generate new keys? Greetings, Sebastian [0] https://metrics.torproject.org/rs.html#details/A4DEEE8F4467621C0A3CB7F4E25C…

2 2

What is the command to view the tor log file on Debian?
by Keifer Bly 08 Aug '20

08 Aug '20

6 8

Availables ports for obfs4 on Fedora
by I.N.R.I. 07 Aug '20

07 Aug '20

Hi To install Tor I try to set a port for obfs4 The ports 22, 80 and 443 are used I wish to find a free port conpatible with the TCP 127.0.0.1 Or an other adress May you help me pls ? Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

Re: [tor-relays] Tor is showing it's running different versions, and continuing previous thread
by Keifer Bly 07 Aug '20

07 Aug '20

That returns "reading config failed" so no luck. Thanks anyway though! --Keifer On Fri, Aug 7, 2020 at 12:43 PM <tschador(a)posteo.de> wrote: > On 07.08.20 20:47, Keifer Bly wrote: > > > Hi all, > > > > So my relay at > > > > > https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36… > > > > Says it is running two different versions, on metrics it is showing it is > > running tor 0.4.3.5 but when I log into the VPS via SSH it says it is > > running tor 0.4.3.6. It has been like this for a few days now. Something > > is also not allowing me to check tors data logs, when I check my torrc it > > says the log file is /var/log/tor/notices.log, it either just loads a > blank > > file or says the file is unwrite able. This is odd I don’t believe I did > > add any special configuration for this. > > Hi Keifer, > > on Debian you can check: tor -v; dpkg -l|grep "ii ?tor" > For me it shows: > Tor 0.4.3.6 running on Linux > ii tor 0.4.3.6-1~d10.buster+1 > ii tor-geoipdb 0.4.3.6-1~d10.buster+1 > > Next - check: ls -lA /var/log/tor > An my server it shows: > -rw-r----- 1 debian-tor adm 0 Jul 13 21:03 log > > The owner should be "debian-tor" or whatever your tor is running. > use: chown to change file owner and group > and: chmod to change file mod bits > > Good luck! >

1 0

Tor is showing it's running different versions, and continuing previous thread
by Keifer Bly 07 Aug '20

07 Aug '20

Hi all, So my relay at https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36… Says it is running two different versions, on metrics it is showing it is running tor 0.4.3.5 but when I log into the VPS via SSH it says it is running tor 0.4.3.6. It has been like this for a few days now. Something is also not allowing me to check tors data logs, when I check my torrc it says the log file is /var/log/tor/notices.log, it either just loads a blank file or says the file is unwrite able. This is odd I don’t believe I did add any special configuration for this. Heads up, on my end the spam emails are coming through again. Cheers. Thanks very much. --Keifer

1 0

The “tor-relay” Well-Known Resource Identifier - IANA registration
by nusenu 07 Aug '20

07 Aug '20

Hi, as already sent to the tor-dev mailing list a week ago I planning to submit a well-known URI registration ( https://tools.ietf.org/html/rfc8615 ) so the verifyurl is at a static place and no longer needs to be specified explicitly. Please let me know if you have any comments. https://nusenu.github.io/tor-relay-well-known-uri-spec/ kind regards, nusenu -- https://mastodon.social/@nusenu

2 1

West Coast US Tor Relays Slow - Low Consensus Weight versus East Coast
by Neel Chauhan 06 Aug '20

06 Aug '20

Hi network-health@/tor-relays@ mailing lists, I noticed one thing: Tor relays on the West Coast US (and Canada) are generally slower than those on say the East Coast and in Europe. I moved to the West Coast this January, but this was not an issue in the past when looking at dedicated servers I had from the West Coast prior to this year. These are two middle relay instances on an Gigabit FTTH connection (Wave G in Redmond, WA): https://metrics.torproject.org/rs.html#details/B0F9BA27944FA59E3B1A182208FF… https://metrics.torproject.org/rs.html#details/DB710B14D7329B7289CFCC547F48… The Consensus Weight often is slower than the Advertised Bandwidth, and isn't ramping up despite having lots of bandwidth. I set RelayBandwidthRate to about 500 Mbps on each instance. This isn't just a Wave G problem, this affects almost every relay in the West Coast including other Gigabit ISPs such as AT&T (AS7018) and Sonic (AS46375), as well as hosting companies and colocation facilities. For instance, my Los Angeles-based Exit relays at Psychz Networks (AS40676) show this issue (however they are new): https://metrics.torproject.org/rs.html#details/156AAC3FAD1ACC8906316519DCB4… https://metrics.torproject.org/rs.html#details/A69CEB30328B1E85C6B167FECAF2… Even Emerald Onion has this issue: https://metrics.torproject.org/rs.html#details/09DCA3360179C6C8A5A20DDDE1C5… What is causing this issue and is there a solution? Is it backbone congestion due to COVID-19? The high load on dirauths? sbws regressions? Can I help fix this issue? I am a Core Tor contributor and am open to also working on sbws. Is there a way to optimize my relays (they run FreeBSD). -Neel === https://www.neelc.org/

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays