-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Application won't progress past Step 3/4 Hidden Service published #3763
Comments
@KISBITCOIN Please include the log files. A screenshot of the UI is not useful for debugging this. bisq.log from here: https://docs.bisq.network/backup-recovery.html#data-directory |
I wiped the entire application and app support folder and got it to work. |
I've reopened this issue because it has completely stopped my client from working. Logs attached. |
I have the very same issue when I am on "slower" internet connection. My hypothesis is:
Plus, it's burning CPU in meatime like crazy. |
This issue is worked on right now: #4233 |
@chimp1984 has this (and other "3/4" issues) been fixed by #4586 ? |
Not entirely. We have seen those issues still happening. Last weeks Tor was quite unstable due the v3 address issues with authority dir dos. So I did not look further what can be the reason for it. I have very slow internet and it happens frequently to me. I assume timeouts on requester or seeds causes it. But would be great if you dig into that. |
Also ran into this issue today as well. Bisq started after I've update to the newest version, restarting it several times and finally waited roughly 5min. OS: Debian/Qubes Logs
|
@Siproqu Can you try again? There seems to have been some issue with seed nodes. |
Today everything went fine. |
Since 3 days I have this issue. After some while it tells me about TOR issues but nothing fixes these. TOR browser works from here. I see in the logs that my BTC node appears to be missing bloom filters but the symptoms are the same when I don't run a local node and the message is that there's an issue with TOR either way. |
Looked at your logs. Never saw those issues before. Maybe try to restart your OS. Have a look in your bitcoin core node if you can see bisq as connected peer. It seems there is a conncetion issue to your bitcoin node which is unrelated to tor. You can also try with a new fresh data dir, just to see if it might be related to some corrupted data. If that works but your normal data directory not, try to delete the spv file and resync.
|
I've seen the very same issue. It started while I was on v1.9.14, then upgrading to v1.9.15 made no difference. I have tried all sorts of things, including deleting spv wallet and rebuilding the bitcoin node from scratch. |
Hm... weird... @alvasw: Do you have any idea? |
I restarted the OS and deleted the SPV files before reporting this issue. I also tried to connect to a different BTC node by not starting my own node but find the information in the UI very limiting and not helpful as to what's going on. Edit: I don't see "GUI Settings -> Network Info" in Bisq. It's stuck on "Connecting to Bitcoin network". When I start bisq without a local bitcoin node, it's stuck on the startup screen, too. No "GUI Settings" button anywhere. |
So ... how can I resume using bisq? Can I down-grade? I think it forced me to up-grade in the first place. |
There will be a new version deployed soon. There have been some fixes with tor issues, hope that will have resolved your issue. But it seems some local issue on your side. |
I tried with both my mobile provider and my landline and both look equal. |
Have you tries with using a local (unpruned) Bitcoin node? |
My local node is not pruned and I have tried with it, although it's not clear to me if bisq did pick it up or if it connected over tor to some other node anyway. |
If you have a localhost node running Bisq use that and for the first time you also see a popup in Bisq. You also see then at your Bitcoin node that Bisq has a connection to it. In Bisq you see that its only 1 BTC node and at Settings/Network you see details. |
I had a similar issue recently. The problem seemed to be related to Bisq dropping connections to the provided bitcoin nodes, but I think it can affect people using their own node also. Something similar to https://groups.google.com/g/bitcoinj/c/R14TzTo-yBI I think it was the case it was trying to look up too many addresses and therefore failing to connect to the nodes. I would reccomend loading up Bisq letting it try and connect for 10 mins and then take a look at your most recent log file. See if there are errors when connecting to the nodes. You can paste here the relevant section or send to me on Matrix: pazza83:matrix.org |
@Giszmo Have you tried to delete the tor dir excluding the hiddenservice dir? |
@HenrikJannsen with a new data directory I see the error that was mentioned above already:
I remain stuck without a clue. To recap, data is not corrupt. TOR is not the issue. Problem exists regardless of me connecting to my Bitcoin node or others. What next? |
Next release will have a new version of BitcoinJ (rebased on upstream) with many bugfixes. Hope that resolves your issue. |
So is there anybody I can hire to look into this? I have funds trapped in Bisq since 3 months and would really like to help the project instead of abandoning it as I guess I have a backup somewhere. Can I try a nightly build instead of waiting for the next release or is that a terrible idea? What are the chances that this upgrade helps me? I just spun up my travel laptop that had worked in Germany and while it now also ran into the TOR issue screen, that closed eventually and it loaded a normal dashboard with my offers but a warning: "We did not receive a filter object from the seed nodes ..." and on the bottom right I see "No seed nodes available". It's running 1.9.15. |
The BitcoinJ work is not completed yet. I dont know the state of it but that is the work branch of the dev: https://github.com/alvasw/bitcoinj/tree/bisq_0.16.3
You have to run 1.9.17: https://github.com/bisq-network/bisq/releases/tag/v1.9.17 |
You can reach out to me for support on Matrix. My username there is |
Old, BTC only, probably no open offers. But I think it's irrelevant as the issue persists even with a fresh data dir.
Sparrow connects just fine to my node but I have tried with other nodes, too in the past, running into the "TOR" issue, as I said above ... but ... Good news: With a new data dir and default nodes I get past 3/4! I now updated bisq to
Thanks 🙏 I might take that offer if things don't resolve today. |
Yes, it should do. Best to leave it for a while and not do anything else with the computer running Bisq whilst is syncs. The older the wallet is the longer it takes. It is good practice to switch to a new data directory after a couple of years or 1,000+ trades. As the older the wallet the more problems it creates doing the SPV reysnc. Older wallets also have to query 1,000s of transactions and I do not think bitcoinj likes this very much. If you can get past 3/4 with a new data directory but not the old one the issue could be with your old data directory. As you have only bitcoin in the wallet you could load the seed into another wallet application and payout the bitcoin from there. https://bisq.wiki/Restoring_your_wallet_from_seed#Restoring_to_a_non-Bisq_wallet Granted the above does not fix the issue about why you were unable to get past 3/4 but it does resolve the issue of the stuck bitcoin. |
I hope you guys can fix this as my bisq really doesn't have many transactions but even if they were thousands, asking the user to start from scratch once he reports issues is a terrible UI. Also my bisq accounts are just old and age is rewarded in the market, so by switching the data directory I start from zero and have to accept worse trades. |
Yes the user experience can be improved. With regards your accounts they can be imported. I suppose if you are not able to wait try the above solutions, if you need assistance importing your accounts reach out to me on matrix. |
I'm back in business. I synced with default bitcoin nodes. It made me restart twice as my bisq thing was also not synced but then it worked. I restarted with my own node again and although the console is full of warnings such as:
it appears to be working "fine" now. With the default nodes I did a successful trade and I see offers with my own node, too. I'm tempted to suggest something was fixed with this last release. |
Yes, BitcoinJ had a critial bug which was fixed in last version and will get a more profound fix in next version. The BitcoinJ errors you posted are known and there since long and also got fixed for next release where we got our BitcoinJ fork rebased on upstream main branch. |
Description
Application is stuck on step 3/4.
Version
1.2.4 Mac Os
Steps to reproduce
Expected behaviour
Actual behaviour
Screenshots
Device or machine
Mac Os Mojave 10.14.6
The text was updated successfully, but these errors were encountered: