UPDATE: See my answer below for instructions, I added a Dynamic DNS and added that as the "Address" in torrc. Once I did that I got the "Self-testing indicates your ORPort is reachable. Excellent." message.
I recently started a relay and it appears to be getting traffic OK but the log shows: "Your server (220.127.116.11:443) has not managed to confirm that its ORPort is reachable." "Your server (18.104.22.168:9030) has not managed to confirm that its DirPort is reachable."
I have ORPort advertised on 443 and binding to 9001.
If I check netstat:
watch -d -n0 "netstat -atnp | grep 9001"
I can see established connections to other Tor relays (I checked the IPs in Atlas).
I tested the port forwarding via YouGetSignal and it says the ports are open. I also tested the ports for outbound traffic via portquiz and they worked fine. Is the not managed to confirm error something I need to actively try to fix? If so, how?
Router: Asus RT-N66U w/DD-WRT
Enabled port forwarding through: NAT / QoS => Port Forwarding
Here is a copy of the Port Forwarding table on my router:
Application | Protocol | Source Net | Port from | IP Address | Port to | Enable Tor-Dir | TCP | [blank] | 63118 | 22.214.171.124 | 63118 | Checked Tor-OR | TCP | [blank] | 443 | 126.96.36.199 | 9001 | Checked
Relay is being assigned the above IP via static lease tied to it's MAC Address. I have checked the IP address via ifconfig eth0 to confirm it has 188.8.131.52 as it's address.