When I try to start Tor Browser (newest version), it returns "Vidalia was unable to authenticate to the Tor software. (Control socket is not connected.)" when trying to connect.
I made no new changes on my system prior to it, it just started happening.
Tor process is NOT running in the background. I have tried setting the authentication method to "cookie" or even "none." I have also tried setting a custom password.
I have tried disabling firewall/anti-virus/etc nothing seems to work.
Trac: Username: bd59903
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Having the same issue with my Tor Browser bundle on OS X 10.6.8 was working fine then started having the authentication issue. I attached a screenshot of the error message.
Trac: Username: KIlledkennyagain Priority: normal to major
Did a system recovery without any luck. Updated Windows.
The official TOR guys gotta know what the problem is? Wtf
I reinstalled windows and it worked, but after i installed openvpn, it stopped working, not sure if was the cause though. Uninstalled it, still didnt work. so frustrating!
So reinstalled my OS again. It worked for about a day then stopped again. I did nothing around the time it stopped to my system. So for some reason something or someone is blocking it after several hours.
if I had to edit my windows host file with something like:
127.0.0.1 *********.com
would that affect tor browser? I notice that is the same ip as is in vidalia settings, though as it is just the local i dont know why.
Chiiph: For what it's worth, I also occasionally have issues like this with the Linux TBB, especially after a reboot if my laptop crashed/ran out of battery while Vidalia was open.
Trac: Owner: mikeperry to chiiph Keywords: connection, control socket deleted, N/Aadded Component: Tor Browser to Vidalia Version: Tor: unspecified toN/A
Could it be that the socket file is left in a certain state and if the tor process exits without cleaning, the next time tor tries to use it, the socket seems like is already in use?
but it still happens even if use completely fresh tor browser package
Do you still have OpenVPN installed on your system?
no, the only i found to fix it was to do a fresh OS install. when i did that it worked for about a day, then just started giving the same message. When it did this, I had left it on over night and when i woke up it wasnt working. did not even have openvpn installed on computer after fresh OS install. could there have been a connection problem overnight and something on my system or provider somehow blocked it to prevent errors or something?
I'm going to close this ticket, since it is a generic "my Tor failed to start for some reason" ticket. I suggest looking at Vidalia's message log window in this case, or otherwise trying to get rid of services that might be conflicting with Tor's choice of ports.
Trac: Resolution: N/Ato not a bug Status: new to closed