[tor-relays] Please check if your relay has fallen out of the consensus

[denny.obreham at a-n-o-n-y-m-e.net]

   As an update, once I showed the link from OONI to my ISP, they offered
   to move my server to another location at no charge. So the Tor server
   was moved from India to the UK. (Actually, I built a new one from
   scratch.)

   So I will mention here this ISP - Contabo.com - for their great
   customer service and understanding of what Tor represents. They have
   automatically and temporarily blocked my IP address - and informed me
   that they did - 2 or 3 times in the past because they felt it was under
   a DDoS attack, and I'm OK with that. At one point, communicating with
   their support team, one person even wrote this to me:

   We are glad to support your efforts in maintaining these relays, as
   they play a crucial role in fighting censorship and promoting internet
   freedom. Thank you for your ongoing trust and partnership.

   I initially chose them because they have few exit relays (only 12 as of
   today, 4 of them being mine, but there are about 100 other non-exit
   relays). With that kind of service, I'm wondering why they are not more
   popular for exit relays.

   Denny

   On 2024-10-22 15:41, tor-relays at queer.cat wrote:

   >

   >

   > On 22/10/24 12:08, denny.obreham at a-n-o-n-y-m-e.net wrote:

   >> I still haven't found a solution to my problem I stated earlier in
   my email with the subject "Exit relay not in consensus" https://
   lists.torproject.org/pipermail/tor-relays/2024-October/021899.html
   <https://lists.torproject.org/pipermail/tor-relays/2024-October/021899.
   html>

   >>

   >>

   >> The most helpful answers were from Sebastian <https://
   lists.torproject.org/pipermail/tor-relays/2024-October/021909.html> and
   George <https://lists.torproject.org/pipermail/tor-relays/2024-
   October/021918.html>. I contacted the ASN but never received a
   response. My ISP was useless as they jus t repeated "We don't block
   traffic."

   >

   >

   > Iâve gone through the original thread you shared and found an OONI
   result that supports the notion that your ASN (141995) is blocking Tor
   directory authorities. You can view the result here:

   >

   >
   https://explorer.ooni.org/m/20241001034902.297107_US_tor_d6973b06186ed4
   3a

   >

   >>

   >>

   >> As of today, the server is still active and running. You can't find
   it in the metrics but it is still in the consensus <https://consensus-
   health.torproject.org/consensus-health.html?
   #7BDDE0E7607A5F49578768F44CD721793FA2D7AE>.

   >>

   >>

   >> I did not have much time lately and have no clue what I can do from
   this point forward.

   >>

   >>

   >> Denny

   >>

   >>

   >> On 2024-10-22 04:48, Roger Dingledine wrote:

   >>

   >> Hi folks! We're hunting down a mystery where two of our big
   university relays are having troubles reaching the Tor directory
   authorities:
   https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/86
   Can you check to see if your relay is in a similar situation? In
   particular, the situation to look for is "Tor process is still running
   fine from your perspective, but, relay-search (https://
   atlas.torproject.org/) says you are no longer running." If your relay
   is in this situation, the next step is to check your Tor logs, try to
   rule out other issues like firewall rules on your side, and then (if
   you're able) to start exploring traceroutes to the directory authority
   IP addresses vs other addresses. If you need more direct help, we can
   help you debug or answer other questions on #tor-relays on IRC. Thanks,
   -- Roger _______________________________________________ tor-relays
   mailing list tor-relays at lists.torproject.org
   https://lists.torproject.org/cgi- bin/mailman/listinfo/tor-relays

   >>

   >>

   >>

   >>

   >> _______________________________________________

   >> tor-relays mailing list

   >> tor-relays at lists.torproject.org

   >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

   >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20241028/1f545507/attachment.htm>