On 1/5/2017 1:29 PM, anondroid wrote:
> I just set up a handful of new relays, and all of them have something
> like the following in their logs:
>
> [WARN] http status 502 ("Bad Gateway") reason unexpected while
> uploading descriptor to server '154.35.175.225:80'
> [WARN] Received http statu
> On 05 Jan 2017, at 23:26, Toralf Förster wrote:
> Signed PGP part
> On 01/05/2017 10:40 PM, Sebastian Hahn wrote:
> > They send notifications within 10
> > minutes of the beginning of the hour.
> So, if the issue happens at the 11th minute - it would appear 1 hour before
> someone noticed it ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/05/2017 10:40 PM, Sebastian Hahn wrote:
> They send notifications within 10
> minutes of the beginning of the hour.
So, if the issue happens at the 11th minute - it would appear 1 hour before
someone noticed it ?
- --
Toralf
PGP: C4EACDDE 00
> On 05 Jan 2017, at 22:29, anondroid wrote:
>
> I just set up a handful of new relays, and all of them have something like
> the following in their logs:
>
> [WARN] http status 502 ("Bad Gateway") reason unexpected while uploading
> descriptor to server '154.35.175.225:80'
> [WARN] Recei
I just set up a handful of new relays, and all of them have something like the
following in their logs:
[WARN] http status 502 ("Bad Gateway") reason unexpected while uploading
descriptor to server '154.35.175.225:80'
[WARN] Received http status code 502 ("Bad Gateway") from server
'154.35.175.
