forest08 dropped out of the consensus; all authorities think it is down
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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 -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQtr8ZXhq/o01Qf/pow+TRLM+X4xgUCaWjfzAAKCRAw+TRLM+X4 xsIVAP9E6Ijjzt1yt7AtFTUy6TSoTnVjGMgP2A09bZr0TWNseQD/SqWS27zFl2zq wdEZyZfQHArlgB4YHyS7j06gij2GzAo= =XdXh -----END PGP SIGNATURE-----
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
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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 -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQtr8ZXhq/o01Qf/pow+TRLM+X4xgUCaWl1rwAKCRAw+TRLM+X4 xq+dAQDzjFYVoTreOEAbeVBnpPObhjBFTDx8o5wt16xuoAZxoQEAxxDtxMvLUbrt 0TQvUa6qnWrghy95/XD1ZKTpTwoxmgE= =rvPy -----END PGP SIGNATURE-----
participants (2)
-
forest-relay-contact＠cryptolab.net -
Sebastian Hahn