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

Error Launching Bisq on OSX #2396

Closed
alemiranda19 opened this issue Feb 8, 2019 · 22 comments

Comments

Projects
None yet
5 participants
@alemiranda19
Copy link

commented Feb 8, 2019

Hello,

I had download Bisq 5 times and restart it about 20 times. Not able to make it work. I do not know what the problem is. Any help, please? I always get out at 2/4 Thor Node Create. After that it just disappear without any other massage.

captura de pantalla 2019-02-02 a las 11 30 57

Thanks!

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Feb 9, 2019

Hello @alemiranda19
There are regularly problems with AV and Tor.
If you have an AV running, you should either tell it that Bisq is safe, either try turning the AV off.

I guess that you use the latest v0.9.3 Bisq version ?

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 9, 2019

Thank you, I’m using a IOS OSX computer (macpro) sorry for my ignorance, what is an AV? Yes I had downloaded the latest version.

Thank you

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Feb 9, 2019

apologies, AV = AntiVirus.
Sometimes it could also be a firewall issue.

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 9, 2019

ha,ha

Thanks!

No AV, Malwarebytes OFF, VPN OFF, still the same problem.... Do not really know what the problem is...

thank you for your help.

Alex

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 11, 2019

@ripcurlx

This comment has been minimized.

Copy link
Member

commented Feb 11, 2019

@alemiranda19 Could you please post your log file, so I'm able to see exactly where the initialization fails?

@ripcurlx ripcurlx added the a:bug label Feb 11, 2019

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 11, 2019

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Feb 11, 2019

@alemiranda19
On Mac OSX the logfile is located in : /Users/username/Library/Application Support/Bisq

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

@ripcurlx

This comment has been minimized.

Copy link
Member

commented Feb 12, 2019

This might be the problem, there is no Bisq folder under Application support….

It is hidden by default, so you have to access it like:

Temporary access to the hidden User Library

Method 1:

From the Finder, select the Go menu at top of the screen, and choose Go to Folder.
In the window that opens, enter ~/Library, and click Go.

Method 2:

Go to the Finder (or desktop).
Hold the Option key on your keyboard, and click the Go menu at the top of the screen.
With the Go menu open, you'll notice that pressing and releasing Option will display or hide the Library choice in this menu.
Select Library from the Go menu (while holding down Option) to access the hidden folder.

@ripcurlx

This comment has been minimized.

Copy link
Member

commented Feb 12, 2019

You can also go in the app to Account --> Backup
There is a button to open the log file.

bildschirmfoto 2019-02-12 um 11 18 16

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

@ManfredKarrer ManfredKarrer changed the title Error Launching Bisq on IOS Error Launching Bisq on OSX Feb 12, 2019

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Feb 12, 2019

feb.-11 12:38:44.509 [NetworkNode-9999] ERROR b.n.p.n.TorNetworkNode: Could not connect to running Tor: Unsupported private_key algorithm. Did Tor get a new key type for hidden services?

ping @freimair
Does this message help us understand what happens ?

@freimair

This comment has been minimized.

Copy link
Member

commented Feb 13, 2019

Well that should never happen. It basically says that Tor refuses the connection. I will look into these mechanics again once the upcoming monitor release is out.

@alemiranda19 did you try to use an existing Tor instance?

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 13, 2019

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 19, 2019

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Feb 19, 2019

@alemiranda19 ,
There should be a new release (v0.9.4) in the next days.
With new features which may help to solve this issue.
So the best is to wait just those few days, and to see how it works.

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 19, 2019

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Feb 21, 2019

I just had the same error at release testing as well. Seem that the created key at first startup is invalid, at least I tried then the first back up key and that was causing the same error. Good thing is that at that moment deleting the hiddenservice directory has no consequences as no trades/offers/disputes are done.

@freimair We should put that issue on our high prio list. The error message seems to come from netlayer, maybe that could be more clear as well.

@freimair

This comment has been minimized.

Copy link
Member

commented Feb 26, 2019

hm. yes. will look into it.

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Feb 28, 2019

@alemiranda19

This comment has been minimized.

Copy link
Author

commented Mar 24, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.