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 couldnt be taken #2785

Closed
dunkfan opened this issue Apr 25, 2019 · 8 comments

Comments

Projects
None yet
4 participants
@dunkfan
Copy link

commented Apr 25, 2019

An error occurred when taking the offer.

A timeout occurred.

No funds have left your wallet yet.
Please try to restart your application and check your network connection to see if you can resolve the issue.
bisq.log
Please try to restart your application and check your network connection to see if you can resolve the issue.

@ripcurlx

This comment has been minimized.

Copy link
Member

commented Apr 26, 2019

@dunkfan Did this happen to you once when you tried to take this specific offer or every time and for any offer you tried to take?

Apr.-26 00:26:04.625 [JavaFX Application Thread] ERROR b.c.o.a.OfferAvailabilityProtocol: AckMessage for OfferAvailabilityResponse failed. AckMessage=AckMessage{
     uid='672afa79-3bc8-4d81-9951-ea003cd8d5b8',
     senderNodeAddress=klgpg3m7xu36yqkd.onion:9999,
     sourceType=OFFER_MESSAGE,
     sourceMsgClassName='OfferAvailabilityResponse',
     sourceUid='c39f4490-f2ec-462f-9277-9e9b8e3dfde8',
     sourceId='86436211-4d14de04-ed77-4d58-bb44-6f5270cfb1ad-101',
     success=true,
     errorMessage='null'
} NetworkEnvelope{
     messageVersion=10
}, makersNodeAddress=rczscnooqxftn2zo.onion:9999, errorMessage=We did not send the EncryptedMessage because the peer does not support the capability. 
Apr.-26 00:26:13.526 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerSocketHandler: [r3dsojfhwcm7x7p6.onion]:8333: Timed out 
Apr.-26 00:26:13.526 [BlockingClient network thread for r3dsojfhwcm7x7p6.onion:8333] ERROR o.b.n.BlockingClient: Error trying to open/read from connection: r3dsojfhwcm7x7p6.onion:8333: Connect timed out 
Apr.-26 00:26:13.533 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerGroup: [r3dsojfhwcm7x7p6.onion]:8333: Peer died      (8 connected, 0 pending, 9 max) 
Apr.-26 00:26:13.540 [BlockingClient network thread for r3dsojfhwcm7x7p6.onion:8333] INFO  o.b.c.PeerGroup: [r3dsojfhwcm7x7p6.onion]:8333: Peer died      (8 connected, 0 pending, 9 max)

It looks like there was a connection problem with your trading peer. Was the offer still available in the offer book after the error? It might be the case that the peer just stopped the client.

I also saw following warnings regarding the deposit transaction. Not sure if this is something that can be ignored in that case.

Apr.-26 00:27:23.655 [JavaFX Application Thread] WARN  b.c.trade.Trade: depositTx is null 
Apr.-26 00:27:23.671 [JavaFX Application Thread] WARN  b.c.trade.Trade: depositTx is null

Either the deposit transaction wasn't created or the depositTxId or takeOfferDate was null. As the takeOfferDate is initialized in the constructor it is probably the depositTxId that was null in that case.

@ManfredKarrer Is it the case if the deposit transaction is never sent out that it will be reseted on time out and creates this kind of warning. Just to be sure we are not overlooking some issue.

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 27, 2019

@dunkfan What is your banks country?

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 27, 2019

Please also update to latest version 1.0.1.

@marian001

This comment has been minimized.

Copy link

commented Apr 27, 2019

This issue happened to me as well. I'm on version 1.0.1. Attaching log file.
bisq.log

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 28, 2019

@marian001 Which country is your bank?

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 28, 2019

Some countries are blocked atm due to chargeback scams. See https://bisq.community/t/urgent-certain-banks-banned-until-further-notice/7420/

@marian001

This comment has been minimized.

Copy link

commented Apr 28, 2019

@marian001 Which country is your bank?

Germany

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Apr 28, 2019

German banks are banned atm due to the chargeback issues. With next version we add more protection tools and we will unblock it afterwards.

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.