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

Localhost.9999 bug #4123

Closed
leo816 opened this issue Apr 6, 2020 · 4 comments · Fixed by #4154
Closed

Localhost.9999 bug #4123

leo816 opened this issue Apr 6, 2020 · 4 comments · Fixed by #4154
Labels
a:bug is:critical https://bisq.wiki/Critical_bug on:Linux

Comments

@leo816
Copy link

leo816 commented Apr 6, 2020

Description

User's onion address shows up as localhost.9999 and he is not able to receive any messages (on two cases it was the seller)
another mediator (@Bisq_Knight) had another case.

Version

1.2.9

Steps to reproduce

Dealing with two mediation disputes I came across this.

Expected behaviour

a normal onion address.

Actual behaviour

It's simply not possible to get localhost as a network address.

Screenshots

bisq error

Captura de pantalla 2020-04-05 a las 23 50 35

Device or machine

Additional info

@ripcurlx ripcurlx added a:bug is:critical https://bisq.wiki/Critical_bug labels Apr 7, 2020
@ripcurlx
Copy link
Contributor

ripcurlx commented Apr 7, 2020

I think this is related to people using Bisq on Tails as far as I remember. @freimair Could you have a look at this? Thanks!

@freimair
Copy link
Contributor

freimair commented Apr 8, 2020

duplicate of #3927

@freimair
Copy link
Contributor

freimair commented Apr 8, 2020

I propose 2 steps:

  • make it clear that useLocalhostForP2P cmdline option is for debugging and testing purposes only. In turn, if this option is set, set the base currency network away from BTC_MAINNET. That way, we cannot end up in the situation mentioned above.
  • of course, that would disable Bisq for Tails users. Need to figure out what to do.

@freimair
Copy link
Contributor

https://bisq.wiki/Bisq_on_tails

thus, the issues #3927, #2278, #3791, #2841 can finally be closed properly (most of them already have been dropped already anyways)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug is:critical https://bisq.wiki/Critical_bug on:Linux
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants