Bitcoin network failed because of an error:

“Warning: Connection to the Bitcoin network failed because of an error: java.lang.IllegalStateException: Expected PENDING or IN_CONFLICT, was BUILDING.”

I have deleted the old files, but it doesn’t work.
any advice?
.

I would first make a backup : Backing up application data - Bisq Wiki

and then do an SPV resync: Resyncing SPV file - Bisq Wiki

1 Like

Same issue. I have a backup from 1.5 yrs ago. If I’m getting this error message and can’t get in to Bisq then how can I create a new backup? I copied my previous backup into another location, and then deleted the spv file as instructed in the wiki. No result, just keep getting “Warning: Connection to the Bitcoin network failed because of an error: java.lang.IllegalStateException: Expected PENDING or IN_CONFLICT, was BUILDING.” Was working this morning, now nothing. Have a trade pending too.

A backup from 1.5 years ago will rescue your wallet, but not the data created from Bisq afterwards so if you have a trade pending, don’t use that.
Make sure Bisq was updated to the last version.
The issue that generates that error message is solved with a spv resync, which consumes a lot of resources and takes longer if the wallet was created long time ago, and if you restart Bisq it will start from 0. Connecting Bisq to your own BTC node reduces the frequency of this error and makes SPV resync faster.

Thanks for taking the time to comment. In going the SPV resync rout, I have deleted the “bisq.spv chain”. I restart bisq and get the same error message. I close the message, it continues for awhile until I get the message about TOR connection (I tried deleting old files, and connection with bridges). So from there I should hit “close” instead of “shutdown”, and let it sit at the load up screen and eventually something will happen hours or days down the line? That is fine, just want to confirm this is the part that “consumes a lot of resources and takes longer if the wallet was created long time ago”.

Finally building my node next week so hopefully that helps.

i.e. this is the screen I’m sitting at…

image

I’m getting the same issue. I have an Aug 22 backup, but I have an open trade, and also new Revolut account that is in the 30 day verification. I’d preferably like to retain this and the data. Is there some way to restore the old backup and then migrate the missing data/accounts?

Also, with regards to my open trade. I completed my steps and transferred the funds. I was waiting on the seller to confirm receipt of funds before releasing to my wallet. Am I correct to assume that these funds will be in the restored wallet is I restore the old backup?

Lastly, how do I update bisq without accessing the admin panel? Can I download the latest release and transfer to the applications folder (mac)? And then run the application?

I’m still sitting at the same spot 24 hours later…

image

I’m no expert but I don’t think that is the solution. I don’t think the screen you’re sitting on will resolve.

My understanding is that you need to access the dashboard and run this solution.

https://bisq.wiki/Resyncing_SPV_file#From_the_file_system

But obviously if you can’t get to the dasboard then you can’t run that solution.

I just want to add that I don’t appear to have file btc_mainnet/wallet/bisq.spvchain

If I need to resync this file from within the filesystem, I don’t actually have this file currently.

Double checked and I was already using the latest version when this error happened, downloaded on 2/12. Downloaded again and used the repair option. No difference, still can’t get into bisq. Is there a next step after deleting the spv file or am I SOL? I do have bitcoin sitting in that wallet that hasn’t been transferred yet. More concerned about that than the pending trades.

It might be a network issue preventing you from connecting

See: Troubleshooting network issues - Bisq Wiki

Things to try:

  • Can you connect to Tor from your computer with Bisq installed?
  • Connect to Bisq using another internet connection, eg try connecting via your phone
  • Switch the router on and off and re-try
  • clear the Tor cachefiles