GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Louvian Lyndal <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Georg Koppen <[email protected]>,
	bad-relays <[email protected]>,
	 "GNU/Weeb Mailing List" <[email protected]>
Subject: Re: Your TeaInside relay is failing to relay exit traffic
Date: Thu, 25 Aug 2022 14:33:59 +0700	[thread overview]
Message-ID: <CAP2ubg+YF+asicgok0Or1EkWOM8hmMq2OcBJPvDya27v6+DXKQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

On Thu, Aug 25, 2022 at 2:18 PM Ammar Faizi wrote:
> On 8/25/22 1:58 PM, Georg Koppen wrote:
> > Hello!
> >
> > Your TeaInside relay[1] seems to fail relaying exit traffic
> > according to our measurements. We ran some tests and it was not possible
> > in 5/5 cases to reach e.g. https://torproject.org. Could you please look
> > into that and resolve the issue on your end?
> >
> > Please let us know if you have further questions and when the problem is
> > resolved on your side.
> >
> > Thanks for running relays!
> > Georg
> >
> > [1] https://metrics.torproject.org/rs.html#details/F241330F16AF6BD90226CC9130DA8E20B58AAC3B
>
> Hi Georg,
>
> Thanks for reporting this issue.
>
> I will take a look into it. But before that, I have a question. How do I
> test my exit relay to see whether it's working properly?

I checked it, there are many TLS error here:

   TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP
connection reset by peer

I don't understand the reason behind this. Will investigate it.

[-- Attachment #2: tor.log --]
[-- Type: text/x-log, Size: 4401 bytes --]

Aug 25 14:21:21.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:21:32.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:03.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:03.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:17.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:17.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:17.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:36.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:50.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:22:58.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:23:29.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:23:29.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:23:41.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:23:58.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:24:11.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:25:19.000 [notice] TLS error PR_CONNECT_RESET_ERROR while reading with [scrubbed]: TCP connection reset by peer
Aug 25 14:25:47.000 [notice] New control connection opened from 127.0.0.1.
Aug 25 14:26:12.000 [notice] New control connection opened from 127.0.0.1.
Aug 25 14:26:37.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:26:49.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:05.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:20.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:20.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:20.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:20.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:20.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:20.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:26.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:27:40.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:28:10.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:28:33.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:28:36.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:28:59.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:29:26.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer
Aug 25 14:29:33.000 [notice] TLS error PR_CONNECT_RESET_ERROR while reading with 78.42.224.40:9001 ID=C1lV7a6ArdG1jQIwnPXgwMsWmInEiws3R0EGt6TXLxQ RSA_ID=841A6A7A53432F8A6B36D6A3083FE0E29899469C: TCP connection reset by peer
Aug 25 14:29:45.000 [notice] TLS error PR_CONNECT_RESET_ERROR while writing with [scrubbed]: TCP connection reset by peer


  reply	other threads:[~2022-08-25  7:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  6:58 Your TeaInside relay is failing to relay exit traffic Georg Koppen
2022-08-25  7:18 ` Ammar Faizi
2022-08-25  7:33   ` Louvian Lyndal [this message]
2022-08-25  7:48     ` Ammar Faizi
2022-08-25  9:27   ` Georg Koppen
2022-08-25 10:13     ` Ammar Faizi
2022-08-30  5:57       ` Ammar Faizi
2022-08-30 11:02         ` Georg Koppen
2022-08-30 11:14           ` Ammar Faizi
2022-08-30 14:12             ` Ammar Faizi
2022-08-31  0:13               ` Ammar Faizi
2022-08-31  6:37               ` Georg Koppen
2022-08-31  6:45                 ` Ammar Faizi
2022-08-31  7:25                   ` Georg Koppen
2022-08-31  7:48                     ` Ammar Faizi
2022-08-31 12:49                       ` Ammar Faizi
2022-08-31 13:25                         ` Georg Koppen
2022-08-31 13:37                       ` Georg Koppen
2022-08-31 14:02                         ` Ammar Faizi
2022-08-31 14:07                           ` Ammar Faizi
2022-08-31 14:32                             ` Louvian Lyndal
2022-08-31 14:46                               ` Georg Koppen
2022-08-31 14:58                                 ` Ammar Faizi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP2ubg+YF+asicgok0Or1EkWOM8hmMq2OcBJPvDya27v6+DXKQ@mail.gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox