[tor-bugs] #6479 [Tor bundles/installation]: Vidalia was unable to connect to tor. (connection refused by peer.)
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Sun Jul 29 20:49:41 UTC 2012
#6479: Vidalia was unable to connect to tor. (connection refused by peer.)
--------------------------------------+-------------------------------------
Reporter: Torguy01 | Owner: erinn
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor bundles/installation | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------------------------+-------------------------------------
Comment(by arma):
Replying to [comment:4 Torguy01]:
> I'm now getting this. I do not have a antivirus installed and my
firewall is disabled.
>
> ----
> Jul 29 16:21:09.234 [Notice] Tor v0.2.2.37 (git-fce6eb1c44e87bc2). This
is experimental software. Do not rely on it for strong anonymity. (Running
on Windows Vista Service Pack 2 [workstation])
> Jul 29 16:21:10.203 [Warning] Warning from libevent: evsig_init:
socketpair: Connection refused [WSAECONNREFUSED ]
> Jul 29 16:21:10.203 [Notice] Initialized libevent version 2.0.19-stable
using method win32. Good.
> Jul 29 16:21:10.203 [Notice] Opening Socks listener on 127.0.0.1:9050
> Jul 29 16:21:10.203 [Warning] Could not bind to 127.0.0.1:9050: Address
already in use [WSAEADDRINUSE ]. Is Tor already running?
> Jul 29 16:21:10.203 [Notice] Opening Control listener on 127.0.0.1:9050
> Jul 29 16:21:10.203 [Warning] Could not bind to 127.0.0.1:9050: Address
already in use [WSAEADDRINUSE ]. Is Tor already running?
Wait, why are your socksport and your controlport both 9050? Looks like "I
have not changed any settings on Tor." has become no longer true.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6479#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list