- tor-relays - lists.torproject.org

Bridge showing offline
by Eddie 12 Jan '22

12 Jan '22

Looking at tor metrics, one of my bridges is showing as off-line: B080140DC1BAB5B86D1CE5A4CA2EF64F20282440 However, the log isn't showing any issues: Oct 14 00:00:28.000 [notice] Tor 0.4.5.8 opening new log file. Oct 14 00:00:28.000 [notice] Configured hibernation. This interval began at 2021-10-14 00:00:00; the scheduled wake-up time was 2021-10-14 00:00:00; we expect to exhaust our quota for this interval around 2021-10-15 00:00:00; the next interval begins at 2021-10-15 00:00:00 (all times local) Oct 14 01:49:40.000 [notice] Heartbeat: Tor's uptime is 124 days 6:00 hours, with 0 circuits open. I've sent 907.23 GB and received 922.28 GB. I've received 63052 connections on IPv4 and 8375 on IPv6. I've made 512684 connections with IPv4 and 100974 with IPv6. Oct 14 01:49:40.000 [notice] While not bootstrapping, fetched this many bytes: 1801791624 (server descriptor fetch); 175792 (server descriptor upload); 221750347 (consensus network-status fetch); 10974 (authority cert fetch); 19905655 (microdescriptor fetch) Oct 14 01:49:40.000 [notice] Heartbeat: Accounting enabled. Sent: 140.52 MB, Received: 140.69 MB, Used: 281.21 MB / 200.00 GB, Rule: sum. The current accounting interval ends on 2021-10-15 00:00:00, in 22:10 hours. Oct 14 01:49:40.000 [notice] Heartbeat: In the last 6 hours, I have seen 14 unique clients. Initially I thought of a previous issue I had with IPv6 connectivity, but don't think this is the problem here as the 2nd bridge on the same server is showing on-line. Also an IPv6 port scan shows the ports for both bridges as accessible. Ideas ?? Cheers.

5 8

Home Tor Middle Relay Blacklisted
by Gary C. New 10 Jan '22

10 Jan '22

Fellow Tor Operators: After about 9 months of running Tor as a Middle Relay from my home network, I'm beginning to experience signs of my public semi-static IPv4 address being blacklisted with 403 Forbidden errors from Reuters and Venmo. I've confirmed by successfully accessing both sites with my mobile internet connection. I'm not surprised that Venmo is blacklisting, but extremely surprised I'm being blocked by Reuters. You would think such a organization would be a proponent of free speech. I wouldn't be surprised if Reuters used Tor in some capacity. It doesn't make sense. When Googling my public semi-static IPv4 address, it appears in several Tor blacklists. That being said, I'm at the point that, at a minimum, I will have to ask my ISP to freshen my public semi-static IPv4 address. Previously, when speaking with my ISP, they mentioned offering a static IPv6 address at no cost. I'm wondering if that offer was with the expectation that I would have to give up my existing IPv4 semi-static address? If they provided both IPv4 and IPv6 addresses, at no cost, I'd like to run a Tor Bridge using the semi-static IPv4 address and configure my existing Middle Tor Relay to use the new static IPv6 address. That way, I'll be able to browse unimpeded through the semi-static IPv4 address and not have to be concerned with the static IPv6 address being blacklisted. Are other Tor Operators experiencing similar issues? Will I continue to experience blacklisting issues, even after migrating to a Tor Bridge? What are best practices in moving an existing Tor Relay to a new address, while avoiding the loss of flags? As always, I appreciate the feedback. Respectfully, Gary— This Message Originated by the Sun. iBigBlue 63W Solar Array (~12 Hour Charge) + 2 x Charmast 26800mAh Power Banks = iPhone XS Max 512GB (~2 Weeks Charged)

2 1

Overloaded relay - need help with how to debug using MetricsPort
by nottryingtobelame 09 Jan '22

09 Jan '22

The page linked to by the "overloaded" alert on my relay's Relay Search page mentions using MetricsPort for troubleshooting, but it provides no information on how to actually use it. I posted about this issue on Reddit and no one has replied with a viable guide to help me out, though one user was able to find a page showing at least the syntax for MetricsPort. I also reached out to network-report(a)torproject.org and have not received a reply. I found discussion about the implementation of MetricsPort on the Tor Project github but it would be nice if the Tor Project officially documented this, especially since it is suggested in the guidance for resolving this problem. At any rate, my relay is 4.5 years old and I've never had a problem with it being overloaded until now. It is on a Raspberry Pi 4 (4 GB) and that doesn't appear to be anywhere near maxing out CPU or memory usage. The only change I have made is putting it behind a pfSense hardware firewall, but the firewall itself is not maxing out in CPU or memory usage or even storage. So, any help that anyone can provide is greatly appreciated! Thanks in advance!

1 0

Strange thing happening in metrics
by David Hu 09 Jan '22

09 Jan '22

Hello awesome people, I have been running a Tor relay for a while with bandwidth progressively increasing. However in Tor Metrics, it shows like the attached (i.e. consensus weight decreased some, and middle probability as a consequence decreased as well). How is it supposed to happen?

3 2

Leaving tor
by Jonas 07 Jan '22

07 Jan '22

Grüezi, I run a large number of bridges, which hopefully only the tor project can see them and confirm they are mine. I know they are used because I can see the traffic utilization over time. Hopefully they were helpful, especially to people in Russia over the past few weeks. After being harassed by multiple paranoid people over the bridges along with accusations of all kinds, I give up. I do not need this drama. The servers on which the bridges run are good for a while, but I am dropping out of the mailing lists, forum, and matrix. Eventually the bridges will go away too. Merci vilmal and herzlichen glückwunsch! Jonas

2 1

General overload -> DNS timeouts
by Intrepid Ibex 07 Jan '22

07 Jan '22

Hi everybody, I am new to tor (as server operator) and try to support the network by operating an exit node. Machine is running Ubuntu 20.04 - Tor 0.4.6.8. nyx is giving me a notive every 10 minutes or so: [NOTICE] General overload -> DNS timeouts (6) fraction 1.4742% is above threshold of 1.0000% DNS on this machine however works perfectly. I told my tor browser to use my specific exit node, everything works fine. Node is running since 4 days now. Load is as expected. Thanks in advance for any help! Ibex \-- Sent using MsgSafe.io's Free Plan Private, encrypted, online communication For everyone. https://www.msgsafe.io

13 25

Tor relay struggling with circuit creation (CPU Limit)
by GANDI24325_TOR 07 Jan '22

07 Jan '22

Hi Tor relay community, I have recently made a new tor relay, and all is going well however I use NYX to mointor it and over the last day it has been giving the warning message seen below in the nyx mointor, the relay had been running fine for it's first 4 days of life but now shows this message for nealry 30 hours now (scrolling through logs) Also the nyx mointor shows a CPU usage of 80-90% so I know this is the limiting factor and have no issue with it as this server is just free VPS that I am donating so ideally would like it to pump out as much data in/out as possible, but my question is, Do I need to change my torrc to fix this error or will the tor network realize overtime how much traffic is best for this node? Useful information: https://metrics.torproject.org/rs.html#details/448E2528A4AC58A7531EC950AAF0…: GANDI24325second the relay in quesiton, with this website showing everything as fine Family: https://metrics.torproject.org/rs.html#search/family:BC77562EF192F0A580F54D…: the other two relays are working fine Contact info: GANDI24325_TOR [at] protonmail (dot) com Addtional info: If I haven't provided enough infomation/if you want the torrc I can help Thanks in advance for any help Warning messages: 09:10:10 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [2012 similar message(s) suppressed in last 120 seconds] │ 09:09:09 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [1467 similar message(s) suppressed in last 60 seconds] │ 09:08:08 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [628 similar message(s) suppressed in last 60 seconds] │ 09:07:08 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [518 similar message(s) suppressed in last 120 seconds] │ 09:05:57 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [10092 similar message(s) suppressed in last 2820 seconds] │ 08:19:05 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [13039 similar message(s) suppressed in last 120 seconds] │ 08:18:04 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. │ [11034 similar message(s) suppressed in last 60 seconds] │ 08:17:04 [WARN] Your computer is too slow to handle this many circuit creation requests! Please │ consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. ─┘ [7335 similar message(s) suppressed in last 60 seconds]

2 1

Some questions about the uptime requirement
by David Hu 05 Jan '22

05 Jan '22

Hello Tor Relay operators, I am hosting a rather new Tor relay and my uptime is only about 13 hours, while I would like to contribute to Tor by continuing as a relay (NOT an exit one though because of frequent abuse of exit relays and my ISP won't allow it). My question is that I am going to another location for vacation for 3 days and my relay would probably not be up during that time. Does that forfeit my chance to be chosen by clients forever? Thank you! Regards, David

2 1

TOR Metrics showing relay as down but logs show it is apparently active
by Tor Geheimschreiber 05 Jan '22

05 Jan '22

Not sure if this is the correct list on which to ask but a new node created just over 7 days ago is now being shown on Tor Metrics (atlas.torproject.org) as being down. However local logs show heartbeat activity and some directory activity. A port scan of the IP address shows: -- cut here Starting Nmap 7.80 ( https://nmap.org ) at 2022-01-05 14:22 GMT Nmap scan report for [redacted] Host is up (0.018s latency). Not shown: 997 closed ports PORT STATE SERVICE 22/tcp filtered ssh 8085/tcp open unknown 9001/tcp open tor-orport Nmap done: 1 IP address (1 host up) scanned in 1.27 seconds -- cut here /var/log/tor/notices.log shows: -- cut here Jan 05 00:00:34.000 [notice] Tor 0.4.6.9 opening new log file. Jan 05 02:45:49.000 [notice] Heartbeat: Tor's uptime is 6 days 8:42 hours, with 3189 circuits open. I've sent 337.09 GB and received 332.67 GB. I've received 64461 connections on IPv4 and 13628 on IPv6. I've made 106191 connections with IPv4 and 36300 with IPv6. Jan 05 02:45:49.000 [notice] While not bootstrapping, fetched this many bytes: 104491070 (server descriptor fetch); 5940 (server descriptor upload); 11006113 (consensus network-status fetch); 1211313 (microdescriptor fetch) Jan 05 02:45:49.000 [notice] Circuit handshake stats since last time: 632/632 TAP, 172332/172332 NTor. Jan 05 02:45:49.000 [notice] Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 17 v2 connections; initiated 0 and received 0 v3 connections; initiated 2 and received 11816 v4 connections; initiated 113167 and received 63288 v5 connections. Jan 05 02:45:49.000 [notice] Heartbeat: DoS mitigation since startup: 0 circuits killed with too many cells, 0 circuits rejected, 0 marked addresses, 0 same address concurrent connections rejected, 0 connections rejected, 0 single hop clients refused, 0 INTRODUCE2 rejected. Jan 05 08:45:49.000 [notice] Heartbeat: Tor's uptime is 6 days 14:42 hours, with 131 circuits open. I've sent 341.77 GB and received 337.28 GB. I've received 66326 connections on IPv4 and 13652 on IPv6. I've made 108563 connections with IPv4 and 37174 with IPv6. Jan 05 08:45:49.000 [notice] While not bootstrapping, fetched this many bytes: 108020255 (server descriptor fetch); 8064 (server descriptor upload); 11383626 (consensus network-status fetch); 1232744 (microdescriptor fetch) Jan 05 08:45:49.000 [notice] Circuit handshake stats since last time: 193/193 TAP, 57579/57579 NTor. Jan 05 08:45:49.000 [notice] Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 17 v2 connections; initiated 0 and received 0 v3 connections; initiated 3 and received 11912 v4 connections; initiated 115806 and received 65008 v5 connections. Jan 05 08:45:49.000 [notice] Heartbeat: DoS mitigation since startup: 0 circuits killed with too many cells, 0 circuits rejected, 0 marked addresses, 0 same address concurrent connections rejected, 0 connections rejected, 0 single hop clients refused, 0 INTRODUCE2 rejected. -- cut here Any pointers on how to investigate the problem further would be welcome. Thanks, Quentin

2 1

Maybe the next step in russian Tor discrimination
by Tor Relays 03 Jan '22

03 Jan '22

Hello, i have a relay at profitserver.ru at their Chelyabinsk location and recently the relay fell out of the consensus. I can ping all authorities with IPv4 and IPv6 and torproject.org is not blocked. I opened the ControlPort and tried to manually create circuits to the authorities. extendcircuit 0 authoritynickname getinfo circuit-status I observed that i can successfully create circuits to no more than three authorities and it seems to change to which authorities i can create circuits. The unsuccessful circuits stay in EXTENDED but never reach BUILT until Tor gives up eventually. Currently no other of my russian relays are affected. I am not an expert with the ControlPort but i hope this is proving what i tried to prove. Here is the conversation with the support: me: Hello, I am running a (non-exit) Tor relay on the VPS and it stopped working a few weeks ago. I can ping the Tor authorities IP addresses but when i try to manually create a Tor circuit it seems to timeout 6 out of 9 times which indicates some blocking attempts on your (or your upstream providers) side. I have a couple of other Tor relays in russia and i have never seen routinely failing manually created circuits to the Tor authorities. Do you block Tor or do you otherwise mess with Tor traffic? support agent: Hello, i can't say something about TOR network, now. We have black box from government, which can control traffic, and perhaps block TOR. Ourselves don't block TOR me: Thanks for your answer. The TSPU from Roskomnadzor that is doing Deep Packet Inspection? I feel with you and all the russian citizens... :( Good luck support agent: Maybe it's a black box If this is indeed their blackbox messing with Tor traffic then it is quite subtile because it does not block torproject.org and pings to the authorities are going through. The relay suddenly was online for one consensus in the last weeks and i can still use it when i manually set it as a Guard in my Tor client. So if you run a relay in russia and you experience weird stuff with it then you may not only want to check if you can reach the authorities by ping but you may want to try to manually craft a circuit to all of them. Hope that helps anyone Cheers

5 4