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

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 pl ay 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@queer.cat wrote:

On 22/10/24 12:0 8, denny.obreham@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:// [tor-relays] Exit relay not in consensus https://lists.torproject.org/pipermail/tor-relays/2024-October/021899.html

The most helpful answers were from Sebastian <https:// [tor-relays] Exit relay not in consensus> 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:

Tor censorship test result in United States

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? #7BDD E0E7607A5F49578768F44CD721793FA2D7AE>.

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 universi ty relays are having troubles reaching the Tor directory authorities: CMU and Michigan relays having trouble reaching dir auths (#86) · Issues · The Tor Project / Network Health / Analysis · GitLab 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@lists.torproject.org https://lists.torproject.org/cgi- bin/mailman/listinfo/tor-relays

& gt;


tor-relays mailing list

tor-relays@lists.torproject.org

tor-relays Info Page

    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:

I'm pleased to hear that you were able to resolve the issue!

···

On 28/10/24 20:30, denny.obreham@a-n-o-n-y-m-e.net wrote:

    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@queer.cat wrote:

    >

    >

    > On 22/10/24 12:08, denny.obreham@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.
    >

    >>

    >>

    >> 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:

    >

    >
    OONI Explorer
    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:
    CMU and Michigan relays having trouble reaching dir auths (#86) · Issues · The Tor Project / Network Health / Analysis · GitLab
    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@lists.torproject.org
    https://lists.torproject.org/cgi- bin/mailman/listinfo/tor-relays

    >>

    >>

    >>

    >>

    >> _______________________________________________

    >> tor-relays mailing list

    >> tor-relays@lists.torproject.org

    >> tor-relays Info Page

    >

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
tor-relays Info Page

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays