The "first seen" date on my relay
A00E3AAF5A24DC69740FA7A3A1C4A0ECB7972722
Got reset today while I was at work. It's not a problem and I don't
particularly care, but is there anything that would cause this? IP hasn't
changed, Tor version hasn't changed, etc.
Thanks,
Zachary
On Montag, 29. Januar 2024 11:53:25 CET mail--- via tor-relays wrote:
> > If I want to serve an HTML page for my exit node do I need Apache2/nginx
> > or can I just modify my torrc?
I use the simple conf in torrc:
DirPort ser.ver.IP.v4:80
DirPortFrontPage /etc/tor/tor-exit-notice.html
Many rela
Hi,
> If I want to serve an HTML page for my exit node do I need Apache2/nginx or
> can I just modify my torrc?
You don't need a dedicated webserver as long as unencrypted HTTP is acceptable.
You can read more about the default HTML exit notice for Tor exit relays here:
https://community.torpr
Hi.
I am trying several Singapoor relays stuck at 100% bootstrapped
without any coming speed evaluation nor id key attributions,
8B6A6D02A80A7CBB1ED0630150D8D9F9F7D471AF
one middle/guard out of 4/5 came out witn keys an shows in relay
search still without any speed attribution now over 48 hours
If I want to serve an HTML page for my exit node do I need Apache2/nginx or can
I just modify my torrc? ___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays