[tor-relays] New relay has a problem - Re-used IP blocked in consensus?

Hello Tor community! I have some identical new relays, but only one of them has a problem. My intention was an IPv6 problem, so there ist IPV6 diabled at all. Fingerprint: 3F1AE2170CAD31B5694BD9052A2A29E5793BDC1F IP: 107.189.14.123 Ports open: 22, 80, 9001 Test from outside by scanner: ok UFW

[tor-relays] New relay has a problem - Additional info about net config

Here info about netconfig. In the INFO messages is a part of 'Could not get local interface IP address." A mystical thing. root@localhost:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1

[tor-relays] Help a newbie

I have a problem. This relay was running fine until I changed the nickname. After making the change, I ran “tor --verify-config” just to make sure, and then ran “sudo systemctl restart tor@default” I see it running, but the syslog shows: Feb 14 23:31:46 tor1 tor[592]: Feb 14 23:31:46.000 [info]

Re: [tor-relays] Tor Relay Meetup #Fosdem Notes

On Monday, February 7, 2022 9:55:16 PM CET gus wrote: > * Are there instructions for how people can report bugs to IPFire? > > Yes, look at > https://forum.torproject.net/t/tor-relay-search-showing-location-of-some-re > lays-incorrectly/1331 We had an example where a relay operator requested a

[tor-relays] Reduced exit and not IPv4 exit traffic at all

Hello all, how can I used a reduced exit policy and don't allow any IPv4 exit traffic? The following line in the top of all the ExitPolicy lines in torrc seems not to work. ExitPolicy reject 0.0.0.0:* What is the order I needed here, first "reject" and then accept or the other way around? R