# Timeout error when taking offer **URL:** \ **Category:** Support\ **Created:** [April 25, 2019, 6:03pm UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511 "2019-04-25T18:03:11Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![mantesh](https://bisq.community/user_avatar/bisq.community/mantesh/32/2121_2.png) [@mantesh](https://bisq.community/u/mantesh)\ **Post date:** [April 25, 2019, 6:03pm UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/1 "2019-04-25T18:03:11Z")
Im unable to take offers as every time there is a time out error. restarting does not help. My connection seems fine, and is not part of the blocked list. what to do? ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [April 25, 2019, 6:40pm UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/2 "2019-04-25T18:40:24Z")
see [https://github.com/bisq-network/bisq/issues/2773](https://github.com/bisq-network/bisq/issues/2773) and [https://github.com/bisq-network/bisq/issues/2771](https://github.com/bisq-network/bisq/issues/2771) ---
**Author:** ![i-forest](https://bisq.community/letter_avatar/i-forest/32/5_5575768a8748004e209b776fc1b2916d.png) [@i-forest](https://bisq.community/u/i-forest)\ **Post date:** [April 27, 2019, 6:58am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/3 "2019-04-27T06:58:35Z")
Hi, I have the same effects. Ubuntu 18.04 / V0.9.8. Apr.-27 09:06:40.139 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null Apr.-27 09:07:22.230 [JavaFX Application Thread] ERROR b.c.t.p.TradeProtocol: Timeout reached. TradeID=9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101, state=PREPARATION Apr.-27 09:07:22.264 [JavaFX Application Thread] WARN b.c.t.p.TradeProtocol: cleanupTradableOnFault tradeState=PREPARATION Apr.-27 09:07:22.265 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade Z6ghiti3-03ea6cd7-b15d-49a7-a649-0db32c6356b5-098 Apr.-27 09:07:22.265 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade s9gtdp-99e844c3-00e0-4f7a-b368-46f1eeee2fad-098 Apr.-27 09:07:22.265 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade s9gtdp-99e844c3-00e0-4f7a-b368-46f1eeee2fad-098 Apr.-27 09:07:22.266 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade upn5b-bca75497-0813-4b29-8df2-4bb4d5f68ea9-101 Apr.-27 09:07:22.266 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade upn5b-bca75497-0813-4b29-8df2-4bb4d5f68ea9-101 Apr.-27 09:07:22.266 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade upn5b-bca75497-0813-4b29-8df2-4bb4d5f68ea9-101 Apr.-27 09:07:22.267 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 Apr.-27 09:07:22.267 [JavaFX Application Thread] INFO b.c.b.w.BtcWalletService: swap addressEntry with address 1E5feyacXVELuuuigoBP1g274AmxH1KnJk and offerId 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 from context MULTI\_SIG to available Apr.-27 09:07:22.268 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 Apr.-27 09:07:22.269 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 Apr.-27 09:07:22.270 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 Apr.-27 09:07:22.271 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 Apr.-27 09:07:22.273 [JavaFX Application Thread] WARN b.c.t.TradeManager: We found an outdated addressEntry for trade 9pubQ-a4b038ca-b8e1-41a8-9801-45c4ce4e96c4-101 ---
**Author:** ![i-forest](https://bisq.community/letter_avatar/i-forest/32/5_5575768a8748004e209b776fc1b2916d.png) [@i-forest](https://bisq.community/u/i-forest)\ **Post date:** [April 27, 2019, 4:20pm UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/4 "2019-04-27T16:20:50Z")
A new data directory also does not seem to help in accepting a purchase offer. Let’s wait. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [April 28, 2019, 5:06am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/5 "2019-04-28T05:06:45Z")
Which country is your bank? We blocked certain countries because of the scammer. ---
**Author:** ![i-forest](https://bisq.community/letter_avatar/i-forest/32/5_5575768a8748004e209b776fc1b2916d.png) [@i-forest](https://bisq.community/u/i-forest)\ **Post date:** [April 28, 2019, 6:31am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/6 "2019-04-28T06:31:11Z")
Old Germany! Land of confusion. I have 2 banks that show the sender IBAN. Volksbank and fidor. Sparkasse and Comdirect do not display the IBAN. I try it with fidor. Nothing is happening at the moment. Better than falling for scammers ---
**Author:** ![CBA](https://bisq.community/letter_avatar/cba/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBA](https://bisq.community/u/CBA)\ **Post date:** [April 28, 2019, 7:50am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/7 "2019-04-28T07:50:20Z")
I’m also unable to take offer due to the described error. Tried to take the offer from a \>1 year old SEPA account. Please note that I’m the BTC seller, so I don’t really understand why I should be blocked. Together with the other problem (see [Trade stuck before step 1 - #24 by CBA](https://bisq.community/t/trade-stuck-before-step-1/7245/24)), bisq is currently unusable for me. 🙁 Using bisq 1.0.1. My system info (according to log): os.name=Linux; os.version=4.15.0-39-generic; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot™ 64-Bit Server VM) ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [April 28, 2019, 7:56am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/8 "2019-04-28T07:56:40Z")
> [@CBA](#): > > Please note that I’m the BTC seller, so I don’t really understand why I should be blocked. atm Bisq tries to block the scammer(s). And in some case that implies also impeaching some users to risk getting scammed. ---
**Author:** ![CBA](https://bisq.community/letter_avatar/cba/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBA](https://bisq.community/u/CBA)\ **Post date:** [April 28, 2019, 8:12am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/9 "2019-04-28T08:12:35Z")
> [@Homard](#): > > > [@CBA](#): > > > > Please note that I’m the BTC seller, so I don’t really understand why I should be blocked. > > atm Bisq tries to block the scammer(s). > And in some case that implies also impeaching some users to risk getting scammed. I don’t really understand. Please note that the SEPA account to which I tried to sell BTC was more than a year old. And as I can see from the market data, that offer was very likely later taken by another seller (unique amount). So should I assume I’m blocked? Does this explain both the technical difficulties described when taking an offer and when an offer is taken (see [Trade stuck before step 1](https://bisq.community/t/trade-stuck-before-step-1/7245/24))? ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [April 28, 2019, 8:27am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/10 "2019-04-28T08:27:16Z")
With the tools available atm, the blockage is not fine-grained and is thus larger than we would like. So, there are some normal innocent users which are impacted. That’s bad. But not as bad as being scammed. Be also aware that all the time taken by the few devs to answer on questions repeated again and again is time which is taken on coding the counter-measures to solve the issues. There are many threads here in the forum and on the github about this scam issue. It was also discussed in the last video growth call. Please take some time to read this material. ---
**Author:** ![CBA](https://bisq.community/letter_avatar/cba/32/5_5575768a8748004e209b776fc1b2916d.png) [@CBA](https://bisq.community/u/CBA)\ **Post date:** [April 28, 2019, 8:32am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/11 "2019-04-28T08:32:03Z")
The problem is that the answers are inconclusive and leave no clear indication whether the experienced problems are technical or due to the scam blocking. ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [April 28, 2019, 10:29am UTC](https://bisq.community/t/timeout-error-when-taking-offer/7511/12 "2019-04-28T10:29:28Z")
Yes. We’ll hopefully have more specific appli messages in the next version. Also, quoting Manfred > We prefer to not give too much details to not give hints to the scammer. … It’s not an easy game those days.