bitcoin.conf – Actually unusual concern when attempting to attach Sparrow Pockets to Bitcoin Core

2 views 8:23 am 0 Comments May 29, 2023


I’m actually loosing my thoughts on this. I’m really not a technical noob but in addition not the perfect technican. However issues like this could really be very simple for me.
What I need to do: I simply need to join my freshly arrange Sparrow Pockets to my freshly arrange Bitcoin Core.

Initially, my setup:

  • Bitcoin Core 23.0 on Home windows 10, 64Bit (PC, native community)
  • Sparrow Pockets 1.7.1 on Linux (Laptop computer, identical native community)

I’ve arrange Bitcoin Core on my Home windows PC as standard and blocks are updated.
These traces have been added to the “bitcoin.conf”-file on my Bitcoin Core Home windows node:

rpcuser=person
rpcpassword=password

[main]
rpcbind=127.0.0.1
rpcbind=192.168.178.111
rpcallowip=127.0.0.1
rpcallowip=192.168.178.199/24

The place:

  • “rpcbind” – is the native IP tackle of the Bitcoin Core node on Home windows 10
  • “rpcallowip” – is the native IP tackle of the laptop computer the place Sparrow Pockets is working on
    The subnet masks is “255.255.255.0” so “/24” needs to be fantastic.

I’ve arrange a couple of issues like firewall guidelines and so forth. I’ve pressed on “Check connection” a whole lot of occasions and it didn’t work in any respect. By some means, it instantly labored and I received efficiently linked to Bitcoin Core! I used to be actually completely satisfied, BUT: After closing the pockets and opening once more, it once more will not join in any respect.
Once more, I get the next error message:

Couldn't join:
Test if Bitcoin Core is working, and the authentication particulars are appropriate.
See https://sparrowwallet.com/docs/connect-node.html

I observed one thing actually unusual as nicely:
Once I click on “Check connection” on the laptop computer in Sparrow Pockets, even when Sparrow Pockets reveals the above error, the Bitcoin Core display screen modifications from “You haven’t any pockets loaded” to a pockets that’s named “sparrow” (in Bitcoin Core!) and reveals “0.00000000 BTC” (I didn’t arrange any pockets on Sparrow Pockets but!).

I attempted to do a little analysis on this concern nevertheless it appears to be like like I’m alone with this and really feel kinda silly since I do not get what I’m doing improper ..
I additionally tried disabling the Home windows firewall earlier than connecting Sparrow Pockets to it with none success.

Then I’ve randomly discovered this concern on Github.

I’ve tried the next workaround acknowledged on the Github concern web page:

  • Shutting down Bitcoin Core on Home windows
  • Shutting down Sparrow Pockets on Linux
  • Deleting a folder known as “sparrow” within the Bitcoin Core listing
  • Beginning up Bitcoin Core once more
  • Beginning up Sparrow Pockets once more
    And TADA: It really works! It says “Related to “192.168.178.111:8332”. However just one time! Once I shut Bitcoin Core or Sparrow Pockets once more, it will not join afterwards. It offers me the above talked about error once more. BUT: Once I comply with the workaround that I’ve acknowledged above once more, it really works once more (till I shut Bitcoin Core or Sparrow Pockets and open it once more). So it solely works for some time once I delete the “sparrow” folder within the Bitcoin Core listing.
    However solely till none of each functions get closed. If I achieve this, I’ve to re-apply the acknowledged workaround.

Different unusual issues I’ve observed:

  • Once I do the workaround and are in a position to join Sparrow Pockets to Bitcoin Core, it does NOT present any inbound connection (however Sparrow Pockets says “Related to..”)
  • Once I add “disablewallet=1” to bitcoin.conf, it does NOT even work with the talked about workaround (even when it ought to so far as my understanding is appropriate)
  • When getting into improper authentication credentials on function, it takes a while till I get the error message “Couldn’t join” – once I enter them accurately, it reveals this error message INSTANTLY! I received the sensation that it really CAN join (because the time till the error message reveals up is lower than a second, in comparison with once I enter credentials improper which takes 10-15 seconds till the error message reveals up)

Can anybody inform me what the precise heck is going on right here? That is one of many strangest factor I’ve ever seen in my 20 yr laptop carreer. Positive I might simply to this workaround each time however I really feel kinda uncomfortable to attach/create any pockets with this unusual concern being current.

I ought to point out {that a} VPN software program is working on each machines. In any case, it really works when making use of the workaround even with VPNs on (I’ve enabled the “Native Connections” choices inside each VPN GUIs). Nevertheless it additionally doesn’t work with out following the workaround when each VPN softwares are fully closed and shut down. So the VPN cannot be the reason for this concern I feel.

I actually respect any form of assist!
Is there any chance that it is a severe concern by Sparrow Pockets and never my fault in any respect?

Thanks for any assist upfront!

Leave a Reply

Your email address will not be published. Required fields are marked *