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

Offer has localhost:9999 instead of Tor onion address #3927

Closed
deltahandler opened this issue Jan 31, 2020 · 7 comments · Fixed by #4154
Closed

Offer has localhost:9999 instead of Tor onion address #3927

deltahandler opened this issue Jan 31, 2020 · 7 comments · Fixed by #4154

Comments

@deltahandler
Copy link

Description

Onion address of a trader for Buy BTC for BSQ shows localhost:9999 instead of Tor onion address.

Screenshots

Screen Shot 2020-01-30 at 19 31 46

@djhilli
Copy link

djhilli commented Feb 3, 2020

I have the same problem when I am under tails
bisq start and then make an offer, everything seems to be good but nobody buys it, I then tried to buy my own offer from another computer that I created under tails then comes as an error message user is not online. and it shows on picture "localhost:9999"

If there is no solution that bisq works with tails, the solution below only works to buy, but no one can buy a created offer, please help, because bisq and tails would be the best.

to start:

made authcookie readable:
sudo chmod o+r /var/run/tor/control.authcookie

added iptables rules to to connect to nodes:
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8333 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq
sudo iptables -I OUTPUT 3 -d 127.0.0.1 -o lo -p tcp --dport 8000 --syn -m owner --uid-owner amnesia -j ACCEPT # bisq

and started bisq:
./Bisq --torControlPort 9052 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth --seedNodes=ef5qnzx6znifo3df.onion:8000,s67qglwhkgkyvr74.onion:8000 --socks5ProxyBtcAddress=127.0.0.1:9050 --socks5ProxyHttpAddress=127.0.0.1:9050 --useLocalhostForP2P=True --useTorForBtc=True

@deltahandler
Copy link
Author

@djhilli
The argument useLocalhostForP2P=True is the problem. That causes to use localhost network not Tor. Did you copy that from some doc? If so we should fix that at this place.

@ripcurlx It is not a Linux issue....

@ripcurlx ripcurlx removed the on:Linux label Feb 17, 2020
@ripcurlx
Copy link
Contributor

@djhilli
The argument useLocalhostForP2P=True is the problem. That causes to use localhost network not Tor. Did you copy that from some doc? If so we should fix that at this place.

@ripcurlx It is not a Linux issue....

True, I missed the useLocalhostForP2P option in the start-up command

@djhilli
Copy link

djhilli commented Feb 17, 2020

@ripcurlx @deltahandler

Yes the problem is if you start it in Tails then it won't work without the entry "useLocalhostForP2P", because then no connection to the network will be established. And with the entry you can accept offers both buy and sell, but if you create an offer yourself, the other localhost see: 9999 and this offer cannot be accepted.

But think that only appears in connection with tails, but at least with the above syntax, at least to accept the offers.

as I said Tails + Bisq + public Wifi is a statement people

@Bisq-knight
Copy link

I Have one mediation case where one of parties has localhost as his address(and he doesn't reply, no wonder). Would it be of value to get the logs from the other guy?

@freimair
Copy link
Contributor

freimair commented Apr 8, 2020

@djhilli

Yes the problem is if you start it in Tails then it won't work without the entry "useLocalhostForP2P", because then no connection to the network will be established.

Can you be more specific? Maybe provide Bisq logs without the "useLocalhostForP2P"?

@freimair
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants