- tor-relays - lists.torproject.org

Tor relay stopped working on Ubuntu 18.04 in LXD container after update to 0.4.2.5-1~bionic+1
by Clément Février 02 Jan '20

02 Jan '20

Hello, I am running a tor relay on Ubuntu 18.04 in a LXD container. After upgrading form tor version 0.4.2.5-1~bionic+1 over 0.4.1.6-1~bionic+1, it stopped working. Here what I have in /var/log/syslog Dec 23 13:22:29 tor systemd[1]: tor(a)default.service: Failed to reset devices.list: Operation not permitted Dec 23 13:22:29 tor systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor(a)default.service: Operation not permitted Dec 23 13:22:29 tor systemd[1]: message repeated 2 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor(a)default.service: Operation not permitted] Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Tor 0.4.2.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Read configuration file "/etc/tor/torrc". Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.583 [notice] Based on detected system memory, MaxMemInQueues is set to 6260 MB. You can override this by setting MaxMemInQueues by hand. Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.584 [warn] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible. Dec 23 13:22:29 tor systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor(a)default.service: Operation not permitted Dec 23 13:22:29 tor tor[5887]: Configuration was valid Thank you in advance for you help. Regards, Clément

1 0

Where to run new relays?
by Totor be 02 Jan '20

02 Jan '20

Hi list, I'm planning to go for a full reinstall of my 2 guards in order to upgrade them to CentOS 8 & Tor 0.4.x My current relays (Tor 0.3.5.8 & CentOS7) are running at OVH (France) and I was considering installing the new ones at a more useful location France has the second highest aggregated consensus weight, so I should avoid France, THAT is clear But then I got puzzled: Should I maximise the bandwidth criteria by running the relays in countries having good connectivity and bandwidth (Europe, US...), at the cost of diversity? Should I maximise the geographical diversity (Gabon, Reunion...) at the cost of bandwidth? Alternatively, I could just stop asking stupid questions and make my life easier by reinstalling at OVH... The stats are nice indeed, but I miss clear recommendations in order to make my mind So, any useful recommendation,guys?

3 2

bridge offline
by Anonforpeace 31 Dec '19

31 Dec '19

Hello: I had a power outage recently and I've restarted my bridge i.e. restarted the daemon and tor, and when I check the Relay Search section of Tor Metrics, it's taking a long time for my bridge to show as online again. Also, not sure if this matters, but I am running Linux Mint, and recently upgraded to the latest version, 19.3. Any ideas? Thank you.

3 4

Tor exit relay not publishing sever on metrics?
by John Csuti 30 Dec '19

30 Dec '19

Hello, I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed. Thanks, John Csuti Thanks, John Csuti ‭(216) 236-3309‬ https://www.coolcomputers.info/

3 4

A relays primary entry guards
by [REDACTED] 29 Dec '19

29 Dec '19

Hi, from time to time i see that message in the logs of my guard relay: 21:09:06 [NOTICE] I learned some more directory information, but not enough to build a circuit: We're missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6270/6294). That's ok. We will try to fetch missing descriptors soon. 21:09:06 [NOTICE] Our directory information is no longer up-to-date enough to build circuits: We're missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6270/6294). That's ok. We will try to fetch missing descriptors soon. The message itself is clear to me and i usually dont get any errors related to that but i would like to know for what does a (guard) relay has primary entry guards? I thought only clients need guards so what is a relay doing with primary entry guards?

1 0

toranon (977)?!?
by Kenneth Freeman 28 Dec '19

28 Dec '19

Messing around with my new computer I get this: [warn] /run/tor is not owned by this user, but by toranon (977). Perhaps you are running Tor as the wrong user? Duckduckgo displays hentai results. Go figure.

3 3

Tor exit relay not publishing sever on metrics?
by John Csuti 27 Dec '19

27 Dec '19

Hello, I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed. Thanks, John Csuti Thanks, John Csuti ‭(216) 236-3309‬ https://www.coolcomputers.info/

1 0

Stable flag not appearing on bridge, and is it possible to have bridge reachable on different ports?
by Keifer Bly 25 Dec '19

25 Dec '19

Hey, so my bridge at https://metrics.torproject.org/rs.html#details/386E99371B8CD938248940B754F1… Is suddenly not getting the stable flag despite having been running for weeks on end, was this flag removed for bridges? Also, is it possible to have a bridge running on more than one port? Thanks very much. -- --Keifer

1 0

tor 0.2.9.x reaches end of life on 2020-01-01
by nusenu 24 Dec '19

24 Dec '19

This is a reminder that tor version 0.2.9.x reaches its end of life date in a week (2020-01-01). Please upgrade your relays accordingly to avoid stability and security issues. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… As of 2019-12-24 00:00 UTC there are still over 600 Tor relays making up >5% of the tor network's capacity running tor 0.2.9.x All affected relays: https://metrics.torproject.org/rs.html#search/version:0.2.9%20running:true Relay operators with a consensus weight > 9k and a usable contactinfo field got contacted directly. -- https://twitter.com/nusenu https://mastodon.social/@nusenu

1 0

Tor 0.4.2.5 - Unable to Run Tor Relay on Ubuntu 18.04 LTS VPS
by David Croft 24 Dec '19

24 Dec '19

Hi, I'm unable to start newly setup/configured guard/middle relay Tor version 0.4.2.5 after setup & configuration of Tor on an Ubuntu 18.04 VPS server. I'm already running a couple of Guard relays on Ubuntu 18.04 with the same VPS provider who allows for Tor Guard/Middle relays. I've followed a blueprint for setting up the Tor relay on Tor 0.4.2.5 which worked no problem on 6 other relays I've configured & operated without issue in the last month on Ubuntu 18.04 Tor version 0.4.1.6. I've carefully reviewed the steps I've taken to ensure I haven't made any errors during the setup/configuration process. The issue described here is accompanied by the arrival of 0.4.2.5 & this is, in fact, the first time I've tried to set up a Tor relay on 0.4.2.5. I've also included a screenshot that highlights the issues. I realize there might very well be other possible reasons for these errors, so I keep an open mind & will be grateful for any support or advice. Regards, Toni output from: systemctl status tor(a)default.service ● tor(a)default.service - Anonymizing overlay network for TCP Loaded: loaded (/lib/systemd/system/tor(a)default.service; enabled-runtime; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-12-22 16:33:12 CET; 40min ago Process: 3707 ExecStart=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 (code=exited, status=0/SUCCESS) Process: 4643 ExecStartPre=/usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0 --verify-config (code=exited, status=1/FAILURE) Process: 4642 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d /run/tor (code=exited, status=0/SUCCESS) Main PID: 3707 (code=exited, status=0/SUCCESS)

5 8