Thanks for the explanation. You are right. I mixed up socks port 9050 and control port 9051. Thanks, Klaus Damian Johnson <atagar1@xxxxxxxxx> wrote on 10.12.2011: > Hi Klaus. This is the first I've seen that particular error. What's > happening is that... > - arm has configured TorCtl to listen to the control port (4711) > - TorCtl then receives a message that's invalid according to the > control spec from that port and raised that error > > My guess is that you gave arm the wrong port and there's something > else sending data on that port. Per chance did you confuse the > SocksPort and ControlPort? If you're sure that the port is correct > then please do the following... > - run "telnet localhost 4711 > - enter "PROTOCOLINFO" > > if all is well it should look something like this... > atagar@loki:~$ telnet localhost 9051 > Trying ::1... > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > PROTOCOLINFO > 250-PROTOCOLINFO 1 > 250-AUTH METHODS=NULL > 250-VERSION Tor="0.2.2.13-alpha" > 250 OK > QUIT > 250 closing connection > Connection closed by foreign host. > > Cheers! -Damian > _______________________________________________ > tor-relays mailing list > tor-relays@xxxxxxxxxxxxxxxxxxxx > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays