>> Dec 05 21:17:46.000 [notice] Your IP address seems to have changed >> to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46.000 >> [notice] Our IP Address has changed from 142.4.217.95 to >> 167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE). >> Dec 05 21:18:42.000 [notice] Your IP address seems to have changed >> to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). >> Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed >> from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source: >> METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05 >> 21:18:43.000 [notice] Self-testing indicates your ORPort is >> reachable from the outside. Excellent. Publishing server >> descriptor. Dec 05 21:38:37.000 [warn] Your server >> (142.4.217.95:9030) has not managed to confirm that its DirPort is >> reachable. Please check your firewalls, ports, address, /etc/hosts >> file, etc. Dec 05 21:58:37.000 [warn] Your server >> (142.4.217.95:9030) has not managed to confirm that its DirPort is >> reachable. Please check your firewalls, ports, address, /etc/hosts >> file, etc. >I've gotten this far, not being much good at networking I can't tell >where the problem lies.. do I need to forward something? Check your firewall, and gateway port forwards if the server is behind a NAT. If you're not sure where to start, post the output of "sudo iptables -L"
--Sean _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
