- network-health - lists.torproject.org

Philipp Winter's homepage and Social Media
by joe＠phynd.net 19 Aug '25

19 Aug '25

From the metrics homepage there is a list of metrics that redirects to this page, but these stop in 2016. Also, replacement posts in Twitter (now X) seem to be gone, and no metrics are posted on Mastadon. Can these metrics be fixed and updated ? for example, this page : https://metrics.torproject.org/networkchurn.html links to : https://nymity.ch/sybilhunting/churn-values/ Other locations linked: https://metrics.torproject.org/uptimes.html linked to site updates that stop in 2016 : https://nymity.ch/sybilhunting/uptime-visualisation/ Additionally - Given the very anti-open-availability state of X, and the general lack of public availability, please consider using a different social media to provide updates. When Twitter was publicly available without a login posts were visible, but now these Tor Project posts are locked behind an X login: 1. https://x.com/toratlas 2. https://x.com/torproject

2 1

Error
by Warren Bulmer 19 Aug '25

19 Aug '25

Hello Can you explain why I keep getting this error for every IP I want to query? [Logo]<https://icmec.org.au/> Warren Bulmer Technical Lead - Lighthouse [https://blisttech.com/signature/test/phone.png] 0422 840 818 [https://blisttech.com/signature/test/email.png] wbulmer(a)icmec.org.au<mailto:wbulmer@icmec.org.au> [https://blisttech.com/signature/test/web.png] www.icmec.org.au<https://icmec.org.au/>

2 1

next sync monday 19th of may by bbb
by Hiro 14 May '25

14 May '25

Hello, It would be a good idea to have our first sync by voice on monday 19th of May at 1300 UTC. Here is the link: https://tor.meet.coop/hir-ypg-zzf-pka <https://tor.meet.coop/hir-ypg-zzf-pka> If you are a GSoC student and planning to attend feel free to join the bbb, although this is not required. Cheers, -hiro

1 0

Suggestions and debugging for middle/guard relays and snowflake.
by dragauchemehigh＠yahoo.com 02 May '25

02 May '25

Good morning Tor Project. I have been active in this community for a long time.First ,when I was a beginner, I only donated bitcoins and ran a snowflake-proxy from browser.Then switched to a standalone proxy (compiled from source when I used windows).After that, I switched to Linux (first Mint, than Trisquel because it's fully free as in freedom, FSF supported). The problem with both distros is that snowflake-proxy (using apt package) doesn't work on those distros. It can't connect to a certain host/ website from Tor. I don't remember the output but you could test them in a virtual machine. And a HUGE problem is that /var/log/syslog (or syslog1) is continously filled with those errors, after certain days, I have seen my disk space reduced with 50 GB and I coulnd't figure out why. After many trying, I found out that those files were filled with errors from tor snowflake. PLEASE, post it on debugging in snowflake. After learning to use CLI distros (without GUI), I installed snowflake (with apt) in a debian virtual machine (Qemu-KVM with Virtual Machine Manager). It works as expected, it shows me how much data was sent/received. After that, I decided to delete the snowflake and run a middle/guard relay (again, debian, qemu-kvm). The choice for using qemu-kvm over vitualbox is that virtualbox now depends on the non-free open watcom compiler. This is how I installed qemu-kvm: https://trisquel.info/en/wiki/virtualization-using-kvm. And it was a nightmare to set the tor relay up because port forwarding didn't work (I never tested on virtualbox). My port was not reachable from outside, although I set port forwarding in my router settings. It took me almost 20 hours and 35 tryings to make it work. After so many tryings, I managed to find a solution. Please, post it on middle/relay guard installation tutorial or in debugging section, because almost nobody will be willing to do the work I did to fix the error. I will write it here. And another thing, my ip 95.76.41.164 has 3 relays on https://metrics.torproject.org/rs.html#search/myCuteRelay . Please delete the first and second, because they will never work again, I deleted those VM's. Only the last one will be good. Sorry for my english, I am not a native speaker. So as conlusions: 1) Snowflake proxy doesn't work, at least, on Mint and Trisquel, although they are both based on Ubuntu. And the HUGE problem is that /var/log/syslog (or syslog1) is continously filled with those errors. It can be solved with sudo truncate -s 0 /var/log/syslog. 2) For someone who is using QEMU-KVM to run a middle/guard relay (at least on trisquel), the solution to make the relay work is to execute the following commands on HOST computer (not VM) EVERY TIME THE SYSTEM REBOOTS (or shuts down) BEFORE starting the VM: sudo iptables -t nat -F sudo iptables -Fsudo sysctl -w net.ipv4.ip_forward=1sudo iptables -t nat -A POSTROUTING -s aaa.aaa.aaa.a/aa -o zzz00z0 -j MASQUERADEsudo iptables -t nat -A PREROUTING -i zzz00z0 -p tcp --dport ppp -j DNAT --to-destination bbb.bbb.bbb.bbb:pppsudo iptables -A FORWARD -p tcp -d bbb.bbb.bbb.bbb --dport ppp -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT I wrote with with Italic the commands and with Bold the parameters that MUST be changed, based on each person computer. The command that must be used in order to change them, both on host and vm is ip -c addr show aaa.aaa.aaa.a/aa - (host) the inet address of virbr0 (qemu-kvm) (e.g. 192.168.123.1/24)zzz00z0 - (host) the connection name of local inet address of host (e.g. enp27s0)ppp - (VM) the port chosen in torrc file (e.g. 443)bbb.bbb.bbb.bbb:ppp - (VM) the local inet address of vm and chosen port (e.g. 192.168.123.111:443)bbb.bbb.bbb.bbb - the same address as above but without chosen port (e.g. 192.168.123.111) There is NO functional command that must be run on VM. Just ip -c addr show to see the address. The Network source of VM is the default one (Virtual network 'default':NAT). Not bridge or macvtap device. 3) Please delete the first and second relays created on my ip 95.76.41.164. They won't ever work again. If you have any other questions, please ask me.Please provide me an answer to know that you received and read my email. Thank you and best regards!

1 0

Incorrect Tor Relay Location on metrics.torproject.org
by emmaiscool＠tutamail.com 28 Apr '25

28 Apr '25

Dear Tor Project Network Health Team, I am writing to report an issue with the displayed location of two Tor relays on metrics.torproject.org. Both my relay and my friend's relay are physically located in USA, but the website incorrectly shows their location as the Netherlands. Here are the details of the affected relays: - My Tor relay Fingerprint: 4924C03811F4BF4F7DFAC320A1D0C1D68E12B6CB - My friend's Tor relay Fingerprint: 4BBB3032A9577EF4A11CEB3AF3C115A8FEA11E83 Could you please investigate and correct the location information for these relays? Let me know if you need any additional information to resolve this issue. Thank you for your support in maintaining the Tor network. Best regards, FPS

3 2

set yourself a new password for prometheus / grafana
by Gabriel Filion 17 Apr '25

17 Apr '25

Hello! I'm writing to inform you that TPA's been moving on something that should make it possible to eventually merge both of the prometheus / grafana servers: we're moving towards per-user passwords that need to be set through LDAP and deprecating the shared passwords. I would invite everyone who needs to continue accessing prometheus and grafana (either on prometheus1.tpo or prometheus2.tpo) to head over to https://db.torproject.org/ , login and set yourself a password in the "Web password" field. That field was previously hidden but it was recently added to the form. The password will take some time to get synchronized to the servers, so allow some 1 to 2 hours before you test out your new credentials. When ready, head over to https://grafana2.torproject.org/ and use your ldap username with your new web password to confirm that you're able to login there. The shared passwords that are currently in use are bound to be removed on April 17th. If you're having issues with setting up and/or using your own credentials to access prometheus and grafana, please contact TPA and we'll take a look with you into what's happening. Cheers! additional note for TPA members: we now have a fallback password that's present in our password manager. it should let us access the monitoring sites even if ldap has a disruption. you can try that one as well.

3 6

hiro afk around easter
by Hiro 10 Apr '25

10 Apr '25

Hello, I'll be afk around Easter week, from the 18th till the 23rd of April. Friday 18 and Monday 21 are holidays here so I suppose some of you might be afk too? Since our sync is on monday and I think that is a holiday for most of us I thought we could skip it. Cheers, -hiro

2 1

Relay wrong location
by derekflynn＠vexhub.dev 23 Mar '25

23 Mar '25

https://metrics.torproject.org/rs.html#details/4BBB3032A9577EF4A11CEB3AF3C1… hello that relay saying its in netherlands but its in new york

1 0

My Tor Relay Isn't Working
by dare deleting 22 Jan '25

22 Jan '25

Hi. I've tried to be a Tor relay, but I just doesnt work. I followed your guide, and opened por 9001 and 9002, and the Tor process is active, but my relay just doesnt show on the tor relay lists. Could you help me? Thx!!

2 1

Exit relay count
by Balakrishnan Balasubramanian 11 Sep '24

11 Sep '24

How many exit nodes does tor network have? From https://metrics.torproject.org/relayflags.html , I see more than 2000 exit relays. However `❯ curl --silent -x "socks5h://127.0.0.1:9050" https://check.torproject.org/torbulkexitlist | wc -l ` shows 1144 . Is it because about half of them are not trusted enough to be assigned as exit nodes even though the relay operator is ok with being exit nodes ? -- Regards, Bala

3 2