From: Georg Koppen <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: bad-relays <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Louvian Lyndal <[email protected]>
Subject: Re: Your TeaInside relay is failing to relay exit traffic
Date: Tue, 30 Aug 2022 11:02:46 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
[-- Attachment #1.1: Type: text/plain, Size: 2087 bytes --]
Ammar Faizi:
> On 8/25/22 5:13 PM, Ammar Faizi wrote:
>> On 8/25/22 4:27 PM, Georg Koppen wrote:
>>> There are different ways. One thing we do is to build circuits with the
>>> respective nodes to test as exits and then we try to connect to
>>> different websites and check whether there are any failures. In your
>>> case it seems connections are timing out.
>>>
>>> Another way, which you could try is using Tor Browser with your node as
>>> exit node. For that, after you have downloaded Tor Browser and extracted
>>> it, add to your torrc file (in
>>> tor-browser_en-US/Browser/TorBrowser/Data/Tor):
>>>
>>> ExitNodes F241330F16AF6BD90226CC9130DA8E20B58AAC3B
>>>
>>> The start Tor Browser and try to surf to some websites like popular news
>>> sites etc. Those requests are frequently timing out or take super long
>>> to load resulting caused by lots of circuit churn (as the circuit fails
>>> due to timeouts).
>>
>> Great, thanks for the tips!
>>
>> The latter way using Tor Browser sounds easier for me. I will
>> investigate this and be back to you soon.
> Hi Georg,
>
> I have been trying to investigate this for several days, but haven't been
> able to fix the issue. Looking at the Tor daemon process from htop, it is
> spinning at 100% CPU. I don't know what is going on, but as far as I can
> tell, it is still consuming CPU and network I/O.
>
> I tried to specify my relay fingerprint in torrc Tor browser like
> what you said previously. My Tor browser didn't work. It was always
> timing out with no clear error.
>
> From the server side, this is the last few hundred of lines of my Tor
> daemon log:
>
>
> https://gist.githubusercontent.com/ammarfaizi2/40be0cb122b5ad1240f9001f8e58eb7d/raw/2407fc3063d786e3e0054d522a0e63323e35513e/tor_log.txt
>
> Do you have any suggestion?
>
> If you need more information to diagnose this, tell me what do you
> need. I will happily provide it.
Hrm. What else is running on that server apart from the exit node? Could
you share the torrc file you are using?
Georg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-30 11:02 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
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 [this message]
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=2aba6c4e-04c9-3e66-1293-583e68d8307d@torproject.org \
[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