Opened 3 years ago

Last modified 3 years ago

#22978 needs_information defect

BUG "Could not connect to control port" + Temporary solution

Reported by: wunderbar Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Major Keywords:
Cc: mataspetkevicius98@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Tor browser bundle, currently the latest one available from autoupdates for windows. Gives error "Could not connect to control port", this happens if You edit torrc file at least once, doesn't matter what I change in there, it still gives this error after modifying it. For example I added "ExitNodes $MyExitNodesFingeprintHere" and it triggered this error after trying to launch the tor browser, also trying changing torrc file back to how it was doesn't help, I am not sure why this happens, but the solution is to go to "\Tor Browser\Browser\TorBrowser\Data\Tor" and deleting all the "cached-*" files. And I have to delete them before every launch. I know other people who have experienced this same issue, so this is not unique to me. Windows10 home 64bit. If You need any additional info please let me know, I might have chosen something wrong, for example milestone in this bug report, I am just not familiar with this. I think You will be able to figure it out. Thank You.

Child Tickets

Change History (1)

comment:1 Changed 3 years ago by gk

Milestone: Tor: unspecified
Status: newneeds_information
Version: Tor:

Thanks for this report. I tried to reproduce your problem but to no avail. Could you do the following to help tracking this down?

1) Test whether that happens with a clean, new Tor Browser as well (downloaded from our website)
2) Could you follow the steps in comment:3:ticket:20890 (the place for the latest expert bundle is with and give us the debug log you get when starting Tor Browser with the expert bundle tor.exe?

Note: See TracTickets for help on using tickets.