Hello.
My relay with fingerprint BDB0F71C8EB2572080D38F036E3EB33494500E9E is no
longer being recognized by the consensus. I can confirm that the entire
subnet it is on is able to reach the directory authority's ORPorts, but,
according to the consensus health page, not a single DA reports it as
running. This has lasted for 11 hours so far.
How do I get it back in the consensus?
Regards,
forest
···
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
Hi forest,
your IP is reachable from gabelmoo, but something is preventing me from
talking to its ORPort. You could try a different port, in case someone
blocks "common" relay ports for IPv4, or see if you have some
firewalling in place or anything like that.
Cheers
Sebastian
···
On 15. Jan 2026, at 13:39, forest-relay-contact--- via tor-relays <tor-relays@lists.torproject.org> wrote:
Hello.
My relay with fingerprint BDB0F71C8EB2572080D38F036E3EB33494500E9E is no
longer being recognized by the consensus. I can confirm that the entire
subnet it is on is able to reach the directory authority's ORPorts, but,
according to the consensus health page, not a single DA reports it as
running. This has lasted for 11 hours so far.
How do I get it back in the consensus?
Regards,
forest
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
Hello.
The default IPv4 somehow changed, which caused the firewall rules to
block the port. I've edited /etc/network/interfaces and the ORPort is
reachable again, so it should rejoin the consensus soon. Whoops!
Regards,
forest
···
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org