Re: [tor-relays] Exit relay not in consensus

2024-10-01 Thread boldsuck via tor-relays
On Tuesday, 1 October 2024 19:32 denny.obre...@a-n-o-n-y-m-e.net wrote: >After my last restart I have: > >``` > >Read configuration file "/usr/share/tor/tor-service-defaults-torrc". > >Read configuration file "/etc/tor/torrc". > >Based on detected system memory, MaxMemInQue

Re: [tor-relays] Exit relay not in consensus

2024-10-01 Thread denny . obreham
Before my last restart 6 hours ago you get a series of messages like these: ``` Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 81 v3 connections; initiated 0 and received 341 v4 connections; initiat

Re: [tor-relays] Exit relay not in consensus

2024-10-01 Thread George Hartley via tor-relays
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

[tor-relays] Exit relay not in consensus

2024-10-01 Thread denny . obreham
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?#7BDDE0E7 607A5F49578768F44CD721793FA2D7AE After investigating, I thought the reason was that the IPv6 w