On Thu, Jan 31, 2019 at 6:58 PM Alexander Nasonov wrote:
>
> Matthew Finkel wrote:
> > I opened #29241 for this (because I didn't see anyone else open it).
>
> Thank you! I couldn't submit because trac doesn't accept my password
> anymore.
>
FYI, I think I finally figured this one out, though
> I'd like to add that it's only a warning and my new relay seems to work
> so far:
>
> https://metrics.torproject.org/rs.html#details/839B17C459BCE9FD5178ABD4B2E3493379EC3419
>
I spoke too soon. It went down shortly after my previous email and it
never went back up.
PS See some of you in an
Matthew Finkel wrote:
> I opened #29241 for this (because I didn't see anyone else open it).
Thank you! I couldn't submit because trac doesn't accept my password
anymore.
I'd like to add that it's only a warning and my new relay seems to work
so far:
On Wed, Jan 30, 2019 at 05:23:40PM +0100, Nick Mathewson wrote:
> On Mon, Jan 28, 2019 at 9:52 PM Alexander Nasonov wrote:
> >
> > I recently tried updating one of my relays to Tor 0.4.0.1 compiled
> > with NSS (and without OpenSSL) but it failed to start, see the logs
> > below. I wonder if this
On Mon, Jan 28, 2019 at 9:52 PM Alexander Nasonov wrote:
>
> I recently tried updating one of my relays to Tor 0.4.0.1 compiled
> with NSS (and without OpenSSL) but it failed to start, see the logs
> below. I wonder if this configuration is supported at all and
> whether I should try running a
I recently tried updating one of my relays to Tor 0.4.0.1 compiled
with NSS (and without OpenSSL) but it failed to start, see the logs
below. I wonder if this configuration is supported at all and
whether I should try running a brand new relay instead of updating?
Alex
[warn]
