[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] Re: Relay forest18 is still not on the consensus

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] Re: Relay forest18 is still not on the consensus
From: forest-relay-contact--- via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Dec 2025 23:12:17 -0000
In-reply-to: <20251211082843.275ae00e@ryz.dorfdsl.de>
List-id: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays.lists.torproject.org>
References: <20251211082843.275ae00e@ryz.dorfdsl.de>
Reply-to: forest-relay-contact@xxxxxxxxxxxxx
User-agent: HyperKitty on https://lists.torproject.org/

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello.

Is there any workaround, such as routing connections to the authorities
through a different server, or a way to get the authorities to attempt
to contact my relay via the Tor network rather than directly (only the
authorities seem to be blocked; the rest of the Tor network is fine)?

If not, is there any other way to contribute to the Tor network using
this server? For example, does Snowflake require direct reachability
from the directory authorities?

If the host provider is unable or unwilling to unblock the IPs (or is
unable or unwilling to migrate my server to another DC), and there are
no other ways I can use this server to help the Tor network, I could
settle for a Hyphanet (Freenet) node or I2P router, but I would really
rather use it to support Tor.

Regards,
forest
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvLrj6cuOL+I/KdxYBh18rEKN1gsFAmk7T6gACgkQBh18rEKN
1gv/ABAAj03ForqRUYeZml2kxml/8ydxpKVju+hvbIbhuCwBo+aJwg36q+XVOmP1
OkPw2pJZLvzzU860QczM4SstCXEZx4e4bbQYpPc6ZC6yDEfkNc+AD0O6jiwBsndO
QdYNmnZnFgud/cUgrtTfn7bryqnVFqFoakMbl+MOYCQipVCsnF0dwesTmFVRXojs
XNsxSSFVH3wxwt37tc6hdl9lR9HhzLeftHZI9neg7FtkQ4EhmjNrG/Kf9kxQCw9q
DnCGssSJ72ACMbxWkSxpLOuEXhPEfuLgJl1Yp/8GEe63a1udrIE6xvliIzr0fB7H
My0IBphgoEuX9qE1DnYKQcLeESLg6nGqyixhLqjpgVljLszNhW1mHkmn1tuzPHcg
Mx5rTW5NDsRkR6lzGACxTvZb+1+Z7sAVp073tPCrXn50Lxr58huH4MYcGTF5pvi1
IzVX2kzwwz2G6w3z4F00na++igWBrCbN87Htf5UGyAKz2c/MjC1B0f7AaItej9f9
xh7nztuJuU0kSfGQ44eDUY6klG6c4PPQx0fp3ruyiezVI6+cDBGirIZ6gQLNdLsX
Xt+OAcTb2tARHd7C/KfmIZRB7vJAcCb2vAaGGkNmjfhcw2F7RF3QzBSGwudRHy6l
ZoAHTiZRzdm+lUy138oxdMzuBjjbR9CX6MHwszjRptQRbf2JbJg=
=XlcS
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx

Follow-Ups:
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: Marco Moock via tor-relays

References:
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: Marco Moock via tor-relays

Prev by Author: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by Author: [tor-relays] Re: Questions about running an exit relay
Previous by thread: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by thread: [tor-relays] Re: Relay forest18 is still not on the consensus
Index(es):
- Author
- Thread