> Are you behind a NAT? Yup, that was it. On the day my relay disappeared from the consensus, I reset my modem - having completely forgotten about the port forwarding... So I set up port forwarding and my relay is present again in the Consensus Health.
Thanks for the help! Joep On Wed, Oct 25, 2017 at 12:20 AM, teor <teor2...@gmail.com> wrote: > > On 25 Oct 2017, at 08:35, rasptor 4273 <rasptor4...@gmail.com> wrote: > > However there's also a lot of this in that file: > Oct 24 16:55:45.000 [warn] Your server (24.132.17.230:9001) has not > managed to confirm that its ORPort is reachable. Please check your > firewalls, ports, address, /etc/hosts file, etc. > Oct 24 16:55:45.000 [warn] Your server (24.132.17.230:9030) has not > managed to confirm that its DirPort is reachable. Please check your > firewalls, ports, address, /etc/hosts file, etc. > > > Your relay won't publish its descriptor until it confirms these ports are > reachable. > > Has your IP address changed? > Are you behind a NAT? > Has your provider blocked these ports? > > T > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
