See if you can route to all the authorities.Tor requires that all relays are able to contact all directory authorities.In my case tcptraceroute would not get to all the authorities. For some authorities my ISP was not routing to them.On 8 June 2018 at 17:35, Gunnar Wolf <gwolf@gwolf.org> wrote:Roger Dingledine dijo [Fri, Jun 08, 2018 at 01:20:19AM -0400]:
> First, did your relay find itself reachable (both ORPort and DirPort)
> at startup? Look for lines like
>
> Jun 05 12:47:50.013 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent.
>
> and
>
> Jun 05 12:48:43.824 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor.
Jun 06 15:36:26.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Jun 06 15:36:27.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
So, yes :)
> Second, assuming yes for the first question, I wonder if the directory
> authorities are (still) finding it reachable. You can check the recent
> votes at
> https://collector.torproject.org/recent/relay-descriptors/ votes/
> or try the (easier to use if it works for you) interface at the bottom of
> https://consensus-health.torproject.org/#relayinfo
>
> Maybe your port forwarding is expiring after a little while?
My fingerprint is C0417071C3754885296F4A5935AC1BC1CABDBC31. I see all
authorities give me "V2Dir" and "Valid", but only three (longc,
bastet, moria1) give "Running".
I use my ISP-provided fiber modem. Maybe it is expiring the
connections when idle. Is there a way to request a heartbeat to be
sent?
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor- relays
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays