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

Multiple attempts to take two "Buy BTC" offers - always timeout #2786

Closed
iotatau opened this issue Apr 27, 2019 · 14 comments

Comments

Projects
None yet
4 participants
@iotatau
Copy link

commented Apr 27, 2019

My last "buy" transaction on March 12 had been successful. Today multiple "buy" attempts with Bisq v0.9.7 failed. I am uploading the error log for the time after I had rebooted the PC after the first few timeout errors. Fast network connection (xxx Mbps), no local Bitcoin node running, Tor browser is working fine.
bisq.log

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Apr 27, 2019

Last Bisq release is v1.0.1.
So please close everything you can close.
Make backups.
And with everything well closed, update to last version.

@iotatau

This comment has been minimized.

Copy link
Author

commented Apr 27, 2019

Thank you for your comment. The application had not alerted to the new version.
I have upgraded to v1.0.1 successfully, rebootet the device, next buy attempt - timeout. Log:
bisq2.log

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Apr 27, 2019

There was indeed an issue concerning alerting about new version.
(which is or will be solved with next version).
Thanks for the logfile, but is your error still there, or not ?

@iotatau

This comment has been minimized.

Copy link
Author

commented Apr 27, 2019

Yes, as mentioned (" - timeout") I had obtained a timeout after the upgrade. Just now, for this message, I have tried to take a third offer, again a timeout.

@sejktmcsdlmfhsc

This comment has been minimized.

Copy link

commented Apr 27, 2019

Hi, there, same issue on my side(bisq 1.0.1):
timeout on taking the offer. in the log it says:
WARN bisq.core.trade.Trade: depositTx is null

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 27, 2019

@iotatau Is it always the same offer or different ones? Can you post the offer details (currnety, payment method, buy or sell, price? Can you post your onion address?

@iotatau

This comment has been minimized.

Copy link
Author

commented Apr 27, 2019

Hi @ManfredKarrer Thanks for tuning in. I have tried three different offers, each one multiple times.
My onion address is vw7sbw37esoexacy.onion:9999
I have just obtained another timeout for offer 27829132-3bf18a84-5d59-42b2-be83-bc86004cda0c-101
All attempts were in the "Buy BTC" section with EUR.

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 27, 2019

Which country is your bank account?

@iotatau

This comment has been minimized.

Copy link
Author

commented Apr 27, 2019

Germany. - If you have an option to switch on tracing I could try another attempt for a defined offer.

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 27, 2019

That falls into the blocked countries and that is why you get rejected by the peer and that causes a timeout. We are working on a release with more protection against that chargeback scammer and then we can release the ban again. Please wait 1-2 weeks until that is out.

@iotatau

This comment has been minimized.

Copy link
Author

commented Apr 27, 2019

Thank you for clarifying.

All the best.

@sejktmcsdlmfhsc

This comment has been minimized.

Copy link

commented Apr 27, 2019

Dear @ManfredKarrer could you explain the "blocked countries"?
Or is there a discussion/FAQ on the bisq forum where I can read about it?
Does the blocking come from bisq client?
In my case it was also EUR - DE.
Thank you!

@iotatau

This comment has been minimized.

Copy link
Author

commented Apr 27, 2019

@sejktmcsdlmfhsc

This comment has been minimized.

Copy link

commented Apr 28, 2019

thank you so much @iotatau !

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.