Hi Teor,

I've restarted tor, please see attached the notice logs I've uploaded to debian's pastebin: https://paste.debian.net/hidden/133a9cb5

Thanks & best regards.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 21 de September de 2018 0:46, teor teor@riseup.net wrote:

On 21 Sep 2018, at 04:26, T0r-n0d3 t0r-n0d3@protonmail.com wrote:

...

I recently migrated my tor node to new hardware: t0rnod3 5582BBEC12380E34D7DFB8C237939A0B317B205E

Copying the /var/lib/tor/keys/ folder on the process. Now my node do not handles circuits, nor it's shown in atlas and I see the following on the logs: [notice] Heartbeat: It seems like we are not in the cached consensus.

What does your relay log when it uploads its descriptor to the directory authorities?

Please restart your relay, and send us your notice-level logs via a pastebin service.

https://paste.debian.net/ is accessible over tor, for those of us who use Tor Browser.

T

That did the trick, thanks.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 21 de September de 2018 18:29, nusenu nusenu-lists@riseup.net wrote:

T0r-n0d3:

...

Hi Teor, I've restarted tor, please see attached the notice logs I've uploaded to debian's pastebin: https://paste.debian.net/hidden/133a9cb5

some observations:

• "ORPort is reachable from the outside. Excellent." -> good

• you have an IPv6 ORPort: Common issue: IPv6 enabled but not actually working

• you have hibernation enabled

  only the 3 non-IPv6 directory authorities consider your relay running.

  Try to temporarily disable the IPv6 ORPort line and see if that solves your problem.

  -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu