GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
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: Wed, 31 Aug 2022 06:37:01 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


[-- Attachment #1.1: Type: text/plain, Size: 1066 bytes --]

Ammar Faizi:
> On 8/30/22 6:14 PM, Ammar Faizi wrote:
>> On 8/30/22 6:02 PM, Georg Koppen wrote:
>>> Hrm. What else is running on that server apart from the exit node? 
>>> Could you share the torrc file you are using?
>>
>> I run a single Tor process. Apart from the exit node, it runs:
>>
>>     - TransPort
>>     - DNSPort
>>     - and many socks5 proxies
>>
>> torrc file is:
>>
>>    
>> https://gist.githubusercontent.com/ammarfaizi2/7b6bef9eafc4c33085a893044eab8187/raw/38f47e88f812a7f092b3b5e8486399c59080d8d2/torrc.txt
> Hi Georg,
> 
> Follow up on this issue...
> 
> My exit node is now working properly. I also have just re-activated
> the IPv6 support on it. My Tor browser is now working fine and I can
> confirm the exit IP matches with my exit node server.
> 
> While I don't actually know the reason behind this issue, it's all
> fixed now. I also learned more about Tor network.

Great, what did you change?

Georg

> Thanks for reporting and helping!
> 
> Please let me know if I missed something.
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-08-31  6:37 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
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 [this message]
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=0238b664-2822-7db1-da0e-3f4424737b51@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