Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error occurred at initializing Bisq: bisq.tor.controller.ControlCommandFailedException: Couldn't connect to control port.. #2239

Closed
Sniggly opened this issue Jun 2, 2024 · 3 comments · Fixed by #2288
Assignees
Labels

Comments

@Sniggly
Copy link

Sniggly commented Jun 2, 2024

bisq2 issue.txt

@HenrikJannsen
Copy link
Contributor

HenrikJannsen commented Jun 3, 2024

Could you also post the tor debug logs (from inside the tor directory)?

Can you check if there is any tor process running after shutting down Bisq? If so can you kill it and try again?
Does the exception come each time you start? If so try to restart the OS.

@Sniggly
Copy link
Author

Sniggly commented Jun 4, 2024 via email

@HenrikJannsen
Copy link
Contributor

At Settings/Utils you can open the data directory. There is a tor folder inside and there the debug.log

alvasw added a commit to alvasw/bisq2 that referenced this issue Jun 11, 2024
On Windows Tor writes its control port number to a file before the port
is accessible by other applications. Users reported that Bisq throws a
ConnectException (ControlCommandFailedException) at startup. All logs,
I received so far, are from Windows users.

Fixes bisq-network#2239, bisq-network#2253
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants