On 18 Oct (20:11:45), Markus Koch wrote:
> 20:08:18 [WARN] Received http status code 404 ("Not found") from
> server '86.59.21.38:80' while fetching
> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
> 8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> 20:06:18 [WARN] Received http status code 404 ("Not found") from
> server '194.109.206.212:80' while fetching
> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
> C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '171.25.193.9:443'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '154.35.175.225:80'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '131.188.40.189:80'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '86.59.21.38:80'. Please
> correct.
>
> This is my niftypika server. This is animal abuse! Seriously, WTF is
> going wrong?
Hi!
It turns out that our last change to the dirauth configuration to reject newly
discovered malicious relays had the _wrong_ IPs for the relay fingerprints...
and you relay IP was a victim of this :S ...
My apologize! I'm currently working on fixing this, you should be back in the
consensus once authorities update from the mistake.
Again, sorry!
David
>
> Markus
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays