Re: [tor-relays] Relay out of consensus after node migration

2018-09-21 Thread T0r-n0d3
That did the trick, thanks. Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Friday, 21 de September de 2018 18:29, nusenu wrote: > T0r-n0d3: > > > Hi Teor, > > I've restarted tor, please see attached the notice logs I've uploaded to > > debian's pastebin: > >

Re: [tor-relays] Relay out of consensus after node migration

2018-09-21 Thread nusenu
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

Re: [tor-relays] Relay out of consensus after node migration

2018-09-21 Thread 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 Thanks & best regards. Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐ Original Message ‐‐‐ On Friday, 21 de September de 2018

Re: [tor-relays] Relay out of consensus after node migration

2018-09-20 Thread teor
> On 21 Sep 2018, at 04:26, T0r-n0d3 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 >

[tor-relays] Relay out of consensus after node migration

2018-09-20 Thread T0r-n0d3
Hi, 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