I updated OpenSSL, removed my keys and restarted the Tor service on my Debian relay. Now I have been running it for 3 days and I still haven't gotten any flags and the relay is not visible in Atlas.
Arm keeps saying: "[NOTICE] Our IP Address has changed from 141.101.117.220 to 141.101.116.220; rebuilding descriptor (source: METHOD=RESOLVED HOSTNAME= tor-relay.onlineprivatliv.dk)."
Here's a screenshot: http://puu.sh/8hBlM/71bbcb5aff.png
I am not sure what is going on here. Do you have any idea?
Thanks in advance.
On Mon, Apr 21, 2014 at 05:08:57PM +0200, Niels Hesse wrote:
I updated OpenSSL, removed my keys and restarted the Tor service on my Debian relay. Now I have been running it for 3 days and I still haven't gotten any flags and the relay is not visible in Atlas.
Arm keeps saying: "[NOTICE] Our IP Address has changed from 141.101.117.220 to 141.101.116.220; rebuilding descriptor (source: METHOD=RESOLVED HOSTNAME= tor-relay.onlineprivatliv.dk)."
Here's a screenshot: http://puu.sh/8hBlM/71bbcb5aff.png
I am not sure what is going on here. Do you have any idea?
% host tor-relay.onlineprivatliv.dk tor-relay.onlineprivatliv.dk has address 141.101.117.220 tor-relay.onlineprivatliv.dk has address 141.101.116.220 tor-relay.onlineprivatliv.dk has IPv6 address 2400:cb00:2048:1::8d65:74dc tor-relay.onlineprivatliv.dk has IPv6 address 2400:cb00:2048:1::8d65:75dc
Your host resolves to two different A records.
Tor keeps changing its mind about which one it should use, presumably because of some "randomize the order in which you return the A records" algorithm in some resolver somewhere.
The simplest answer is to set the Address line in your torrc to explicitly tell it your IP address. The better answer is to figure out what's up with your hostname and fix it.
(Also, it seems like it's not reachable? But then, I'm not sure which IP address I should be checking. :)
--Roger
tor-relays@lists.torproject.org