Yup - Me Too...

----- Original Message -----

From: "Aneesh Dogra" lionaneesh@gmail.com To: tor-relays@lists.torproject.org Sent: Tuesday, December 12, 2017 8:47:30 PM Subject: Re: [tor-relays] Issues with faravahar?

On Tue, Dec 12, 2017 at 3:06 PM, r1610091651 < r1610091651@telenet.be > wrote:

Hi

I'm seeing regular issues with faravahar in logs lately. Is somebody working on this?

Logs: Dec 12 10:32:56.000 [warn] HTTP status 502 ("Bad Gateway") was unexpected while uploading descriptor to server ' 154.35.175.225:80 '. Possibly the server is misconfigured? Dec 12 10:33:56.000 [warn] Received http status code 502 ("Bad Gateway") from server ' 154.35.175.225:80 ' while fetching "/tor/server/d/706E3C29265BD073DF77DC457A3CD8B1BC16C6E6+E223A1B036E3F7315DCADE32F6A4428F15148987.z". I'll try again soon.

Thanks

Hey,

I am getting the same warnings in my log files. Running an exit relay.

Thanks

Hello.

I am getting this too, I saw this the logs a few months ago and didn't think anything of it, this time though I ran Wireshark while started tor, and it appears tor is transmitting encrypted info over port 80. I have the .pcap file to prove it.

I started / stopped the relay a few times so I could get a packet capture, unfortunately it was on a Raspberry Pi over SSH, and I couldn't run it for too long or the Pi would grind to a halt, but each time I started it the same / similar error message appeared in the log.

OUTPUT FROM LOG

Dec 11 21:19:17.000 [warn] HTTP status 502 ("Bad Gateway") was unexpected while uploading descriptor to server '154.35.175.225:80'. Possibly the server is misconfigured? Dec 11 21:24:17.000 [warn] Received http status code 502 ("Bad Gateway") from server '154.35.175.225:80' while fetching "/tor/server/d/DC8CB10998F444D76F0734EDB3081B7DFD2823AD.z". I'll try again soon. Dec 11 21:41:17.000 [warn] HTTP status 502 ("Bad Gateway") was unexpected while uploading descriptor to server '154.35.175.225:80'. Possibly the server is misconfigured?

OUTPUT FROM WIRESHARK (select packet > save info as text)

78250 52.230515226 154.35.175.225 192.168.1.102 HTTP 202 HTTP/1.1 502 Bad Gateway

Surely tor shouldn't be transmitting unencrypted messages? I was able to use Wireshark to extract the objects from the conversation and they include (amongst other things) RSA certificates. There is a few HTTP get / put to other IP address as well.

****Is this a bug in tor, or a problem with either my or the remote relay setup?****

I know a few things about Linux, but I am not a programmer by a long shot, and I would be grateful if anyone could help clear my confusion.

Thanks

On Tue, Dec 12, 2017 at 10:54 AM, teor teor2345@gmail.com wrote:

On 12 Dec 2017, at 20:36, r1610091651 r1610091651@telenet.be wrote:

Hi

I'm seeing regular issues with faravahar in logs lately. Is somebody working on this?

faravahar is not voting, so it's probably down: https://consensus-health.torproject.org/

I assume the operator is aware and is working on a fix.

Logs: Dec 12 10:32:56.000 [warn] HTTP status 502 ("Bad Gateway") was unexpected while uploading descriptor to server '154.35.175.225:80'. Possibly the server is misconfigured? Dec 12 10:33:56.000 [warn] Received http status code 502 ("Bad Gateway") from server '154.35.175.225:80' while fetching "/tor/server/d/ 706E3C29265BD073DF77DC457A3CD8B1BC16C6E6+E223A1B036E3F7315DCADE32F6A4428F15148987.z". I'll try again soon.

This is a proxy telling you that the POST request can't be handled by the authority.

T

---

tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

On Tue, Dec 12, 2017 at 1:17 PM, tor tor@anondroid.com wrote:

...

I am getting this too, I saw this the logs a few months ago and didn't think anything of it.

I wouldn't worry about it. Faravahar has a long history of misbehavior:

https://lists.torproject.org/pipermail/tor-relays/2015-November/008097.html https://lists.torproject.org/pipermail/tor-relays/2017-January/011627.html

(and other threads, I'm sure.)

Why don't you guys boot it off the network and replace it with a better-maintained authority server?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 12/12/2017 11:54 AM, teor wrote:

I assume the operator is aware and is working on a fix.

There're since months errors logged here for that machine. I decided to ignore all errors from that machine.

- -- Toralf PGP C4EACDDE 0076E94E