Hi, looks like the DirAuth's think that your relay is unreachable, and so your descriptor isn't published, so your flags are not updated, this would explain the lack of change in flags.

Port 443 on 156.67.111.146 is open for me, can't test IPv6 as I have disabled it through my modem and kernel command line.

Can you attach your tor log file?

You can also adjust the log verbosity of certain "domains" within Tor like so:

https://2019.www.torproject.org/docs/tor-manual.html.en#Log

Please let us know what you find.

Thanks, George On Tuesday, October 1st, 2024 at 1:40 PM, denny.obreham@a-n-o-n-y-m-e.net denny.obreham@a-n-o-n-y-m-e.net wrote:

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?#7BDDE0E7607A5...

After investigating, I thought the reason was that the IPv6 wasn't reachable anymore. It happened once before with another relay. Seems to be a problem with my ISP. Anyway, I just remove the ORPort IPv6 address and IPv6Exit flag from the torrc file and everything should return to normal. It has been days and it doesn't. Reloaded and restarted more than once since then.

What I don't understand is that the OR IPv6 address and the ReachableIPv6 flag are still listed in the metrics. h ttps://metrics.torproject.org/rs.html#details/7BDDE0E7607A5F49578768F44CD721793FA2D7AE

Any help would be appreciated.

.ql-align-left{text-align:left}.ql-align-center{text-align:center}.ql-align-right{text-align:right}p{margin:0;padding:0;line-height:1.231;}blockquote{margin:0 0 0 .8ex;border-left:1px solid #ccc!important;padding-left:1ex}