Oh, thank <insert your favorite deity here>! I thought I was nuts! I'm fixing to update 49 more clients.

Thanks Tim.

On May 18, 2018, at 22:47, teor <teor2345@gmail.commailto:teor2345@gmail.com> wrote:

Hi,

On 19 May 2018, at 13:24, John Ricketts <john@quintex.commailto:john@quintex.com> wrote:

I've been trying to bring a relay up for testing IPv6. Relay name is QuintexAirVPN1. Metrics website says that the OR Port is unreachable on [2620:7:6000::ffff:c759:df51]:80 - which isn't where I set the ORPort - should be 443...

https://metrics.torproject.org/rs.html#details/F7447E99EB5CBD4D5EB913EE0E35A...

Config is as follows:

ORPort 443 ORPort [2620:7:6000::ffff:c759:df51]:443 Nickname QuintexAirVPN1 ContactInfo John L. Ricketts, PhD <john AT quintex dot com> DirPort 80 # what port to advertise for directory connections DirPortFrontPage /etc/tor/tor-exit-notice.html DisableDebuggerAttachment 0 Sandbox 1 ExitRelay 1 IPv6Exit 1 ExitPolicy accept *:* ExitPolicy accept6 *:* NumCPUs 2

Relay Search is showing you outdated data from the 0200 UTC consensus. Notice that the exit policy in relay search is also different from your torrc.

Consensus Health has data from the 0300 UTC consensus. It says your relay is reachable over IPv4 and IPv6 (Running): https://consensus-health.torproject.org/consensus-health-2018-05-19-02-00.ht...

Please wait a few hours for relay search to catch up.

T _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.orgmailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays