Hi
> > I have DirPort 9030 in my config.
> > It is shown in nyx and the tor process listens there.
> > But the relay search page says:
> > Dir Addressnone
> Yep! This is fine and normal, but I agree it is a surprise.
>
> I just opened a ticket in the relay-search component to help future
> rel
Hi all!
I'm operating a TOR Exit on dedicated hardware. The load average is low
(0.07) and the network load is fine (120Mb/sec out of a 1Gb/sec link).
Connections aren't being dropped, and for all I can see things are fine.
However, on the TOR Metrics relay search, my exit consistently shows as
"
Hi
I wanted to share a project that I've been working on which allows
deploying of Tor relays through terraform.
The code and documentation is here:
https://github.com/andrewmichaelsmith/terrator
The focus is on running on cloud hosting providers, currently supported
cloud services are digitaloc
Update your version of tor this is an old issue that has been fixed in the
latest version.
Thanks,
John C.
> On Jan 16, 2022, at 4:17 AM, AMuse wrote:
>
>
> Hi all!
>
> I'm operating a TOR Exit on dedicated hardware. The load average is low
> (0.07) and the network load is fine (120Mb/sec
On Sunday, January 16, 2022 9:34:24 AM CET Richard Menedetter wrote:
> > > I have DirPort 9030 in my config.
> > > It is shown in nyx and the tor process listens there.
> > > But the relay search page says:
> > > Dir Addressnone
> > > Why is it not shown and used by TOR?
Yes, this is new see
>
> The focus is on running on cloud hosting providers, currently supported cloud
> services are digitalocean, vultr and heztner.
You did check the price lists?
signature.asc
Description: Message signed with OpenPGP
___
tor-relays mailing list
tor-
Ah, thanks! I swear I looked through the forum archives and didn't see
that. :P
I'll see if the FreeBSD package maintainers are releasing an update soon.
I'm trying to stick to maintained packages on the Tor box since I don't
have a ton of time to tinker around with it.
On Sun, Jan 16, 2022 at 6
Hi,
in the past I had already written with someone about it. At that time
the entries were not up to date. There was a Gitlab issue about this,
but I can't find it now.
Anyway, the data is not up to date again.
Example: https://apps.db.ripe.net/db-web-ui/query?searchtext=89.58.17.76
vs
htt