It happened to me recently as well I (a similar situation) I had to switch my relay over to a new OS, I had copied the fingerprint over but despite the fact that I had done this, my relay was still assigned a new identity (which is why I am running a bridge now).
From: torix@protonmail.com Sent: Friday, October 26, 2018 6:57 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Restore tor exit node
This happened to me as well this week. I copied over the torrc and keys directory; I thought that was all I needed. But I got a new fingerprint, so the relay is seen as new. Running Tor 0.3.4.8 on freeBSD.
--Torix
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, October 26, 2018 6:49 PM, node47@torsrv.de wrote:
Dear all,
I have the following problem: My VPS-Hoster has deleted my server. Now I reinstalled tor on fresh Debian 9 minimal in version 0.3.4.8 (as before). I also restored my keys from /var/lib/tor/keys and set the datadir in torrc to /var/lib/tor
When I started the tor-service a new ed25519_signing_cert and ed25519_signing_secret_key were generated as well as a new fingerprint. The secret_* files still have the old timestamp but new fingerprint had been created. Now the server is listed 3 times in the relaysearch and my node is known as “new” node instead of getting the old fingerprint and the old flags/status.
Who can assist me in how to do the restore of the fingerprint and how to correct the relaysearch?!
Best regards from Germany Max
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