Hi,
I just activated my first exit relay. (
https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C
) I had the following in my torrc (plus some other things):
SocksPort 0
ControlPort 9052
ORPort 209.141.39.157:443
I have 2 IPs on my server and I wanted To
Thanks Marco.
First, I had to change my ORPort to 9001 with your proposed configuration
because using 443 caused an error => "Could not bind to 0.0.0.0:443: Address
already in use. Is Tor already running?"
Probably because my other Tor instance (hidden service) is using it.
Now I'm just waiting
The second IP is still in "Exit Addresses" with the new configuration ...
https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C
torrc:
Address 209.141.39.157
OutboundBindAddress 209.141.39.157
ORPort 9001 IPv4Only
Denny
denny.obre...@a-n-o-n-y-m-e.net
OK, finally got a configuration that looks like it works:
Address 209.141.39.157
OutboundBindAddress 209.141.39.157
ORPort 209.141.39.157:9001 IPv4Only
ORPort XXX.XXX.XXX.XXX:443 NoListen
ORPort XXX.XXX.XXX.XXX:9001 NoListen
Where XXX.XXX.XXX.XXX is the IP I didn't want to be u
This has probably been addressed before but why isn't the MyFamily value just a
single, unique ID?
If I have the relays with the fingerprints "John", "Jane", and "Alice" and I
want to add "Bob", wouldn't it be simpler (and more logical) to add the unique
MyFamily "Smith" to each torrc file than
trinity pointard wrote ..
> . It's not as easy as having a unique ID, you need to make sure a
> relay can't spoof being part of a family, that's why it requires a two
> way relationship for now, and will probably use some form of signature
> in the future.
Why not take advantage of the proof entr
I received the following message from Tor Weather. According to Tor Metrics,
this exit relay still has no Guard flag.
Another - slightly more recent - exit relay
(25FC41154DCB2CAE3ABD74A8DFCD5B90D2CFFD57) is on the same server and IP,
and still has the Guard flag (although with 0% guard probabil
I've been thinking long and hard about this problem and I'm not sure if an
email address - validated or not - is the best way to achieve the initial goals.
What are the goals of having this validated email address?
1- Inform the operator;
2- Make sure the operator will read the info;
3- Identify
On 10/31/2023 03:09 PM t...@nullvoid.me wrote ..
> My only concern with your solution is anyone can pretend to be the owner of a
> relay.
- What do you have to say to a relay owner that cannot be said publicly?
- What do you have to say that needs a reply?
In the rare cases where you would have
On 11/9/23 16:03, Jonathan Proulx wrote:
> A little while ago one of my relays switched from usually acting as a
> guard node to never acting as a guard node:
>
> https://metrics.torproject.org/rs.html#details/9715C81BA8C5B0C698882035F75C67D6D643DBE3
>
>
> Doesn't matter to me if it's a guard or no
For your firewall settings, you will find everything you need here:
https://github.com/Enkidu-6/tor-ddos/
It is the common setting for most Tor operators.
Although, I don't think it is the source of your problem and I wouldn't worry
too much about it unless it happens repeatedly.
The log in "/
I manage the two following exit relays:
*
https://metrics.torproject.org/rs.html#details/25FC41154DCB2CAE3ABD74A8DFCD5B90D2CFFD57
*
https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C
They are both on the same IP and servers. A few hours ago they lost contact
> According to
>
https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8
F65B5881B7D4C97C
> the relay is back since 1-2 days, good. Exiting to port 22 might lead
> to a lot of complaints ending at your ISP or yourself. Default SSH.
Yes, as I said I put it ba
Relays do restart for different reasons. For example, two of my relays
(the upgrade process is automated on both) were restarted on March
23rd, practically at the same time.
Different OS versions on different machines from different ISP for both
relays.
One was restarted because
You should tweak your web server as presented in this section:
https://github.com/Enkidu-6/tor-ddos?tab=readme-ov-file#first-step-prep
aring-your-system-for-high-number-of-connections
This would most likely solve Out-Of-Memory problems I suspect you are
experiencing.
Denny
O
I tried changing the exit and OR ports, I tried setting
CircuitBuildTimeout to 300, and my ISP keep assuring me they don't
block any port, ever. Some DirAuth still cannot connect with me.
I have about 20 exit relays spread across 11 ISPs, including 4 with
this ISP (each in a differe
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
I still haven't found a solution to my problem I stated earlier in my
email with the subject "Exit relay not in consensus"
[1]https://lists.torproject.org/pipermail/tor-relays/2024-October/02189
9.html
The most helpful answers were from [2]Sebastian and [3]George. I
contacted the
Before my last restart 6 hours ago you get a series of messages like
these:
```
Since startup we initiated 0 and received 0 v1 connections; initiated 0
and received 0 v2 connections; initiated 0 and received 81 v3
connections; initiated 0 and received 341 v4 connections; initiat
My exit relay which has been running for months without a problem has
not been in the cached consensus for days now.
https://consensus-health.torproject.org/consensus-health.html?#7BDDE0E7
607A5F49578768F44CD721793FA2D7AE
After investigating, I thought the reason was that the IPv6 w
20 matches
Mail list logo
