On Jan 9, 2012, at 5:49 PM, Sebastian Hahn wrote:

On Jan 9, 2012, at 5:35 PM, Klaus Layer wrote:

...

Hi,

my relays are getting 500 error while fetching data from authority dizum.

Can someone explain what is happening with this tor authority?

Regards,

Klaus

14:25:51 [WARN] Received http status code 500 ("Internal Server Error") from server '194.109.206.212:80' while fetching "/tor/server/d/C539CB98343680892C46D0A70770E6D0A4A39564+E5A7994519731C2C3349AAA4C2A38CED2CE74457+E8507D31268490E9E4E8A2110E371F1537156C75+E8BCD670FFB8ADF73195BDB9362ACDDB28F704A5+E94B92087B4614CB7F1C9CC1191C383- 7D890C60E+EA71B375FC45F026C854C903887D981CF19B7326+EA9DE146A13B316D2F3D5C2ACF491C068B93FF9D+EB896E11C16C0531D83560D3CBBEF97AF2FFF4D5+ECEBAAF01CA177EEB68A8A6838E4A16- BD54749F6+ED5A60237FDCA188DF30DC380536754DFBF01404.z". I'll try again soon.

dizum's dir port sits behind a web server doing forwarding, so the error is coming from nginx, not from Tor directly. I've CC'ed Alex here who operates dizum, so that he may comment on the issue.

Thanks Sebastian

Looks like dizum is fixed. Some overzealous firewall issue. Thanks for reporting it here!