RPi 5, Bitcoin Core Installed using SNAP, bitcoin.conf not usable

[MadMacks]

I have a RPi 5 running the latest Rpi OS (Bookworm) that I installed Bitcoin Core (26.0.0) on. This seemed to work fine, and when I started Bitcoin Core is successfully downloaded the blockchain and appears to be running fine.

I then decided to install Sparrow Wallet on my MacBook Pro and connect it to the local instance of Bitcoin Core on the RPi. So I went to the Pi, and went opened btw core, click on the on Options, and then click on "Open Configuration File", and get absolutely nothing.

So I spend a terminal window and went to ~/snap/bitcoin-core/common/.bitcoin and manually opened the empty bitcoin.conf file.

I added the following info to configure file to allow connections to local devices...

Code:

rpcuser=myuserid
rpcpassword=mypassword

[main]
rpcbind=127.0.0.1
rpcbind=192.168.1.33
rpcallowip=127.0.0.1
rpcallowip=192.168.1.0/16

If I understand correctly this should tell Bitcoin Core to bind to localhost and to IP address 192.168.1.33, and to allow connections using the ID and password from localhost or any device in the 192.168.1.X range.

I then restarted Bitcoin Core and tried to configure Sparrow Wallet to connect to the local Core server...and I get "Connection Refused" when I test the connection.

So I went back to the RPi and checked the log for Core and I only see the following the log...

Code:

2024-03-31T17:22:32Z Bound to 127.0.0.1:8334
2024-03-31T17:22:32Z Bound to [::]:8333
2024-03-31T17:22:32Z Bound to 0.0.0.0:8333

So, the questions...

1) If Bitcoin Core is installed using SNAP is there some extra install configuration that needs to be done to make Bitcoin Core understand it's not a "plain jane" install?

2) Is there some issue you see in the configure file I've set up?

3) If installing Bitcoin Core using SNAP creates all kinds of PITA issues, can I do a "plain jane" install of Bitcoin Core on my RPi and move the existing downloaded blockchain to the new install without having to redownload the entire thing again?

If I'd know using SNAP was going to introduce issues (assuming it did) to installed packages I'd have done a regular install of Bitcoin Core and skipped using SNAP.

Feedback would be appreciated on the above!

[1715341724]

1715341724

[1715341724]

1715341724

[1715341724]

1715341724

[1715341724]

1715341724

[MadMacks]

Well, never mind...mostly...

The issue, as is usual, was me and my misconfiguration....

I went back in to the config file and changed it to...

Code:

server=1
rpcuser=myuserid
rpcpassword=mypassword

[main]
rpcbind=127.0.0.1
rpcbind=192.168.1.33
rpcport=8335
rpcallowip=127.0.0.1
rpcallowip=192.168.1.0/16

Restarted, and the config was loaded and I can now connect using port 8335...

I still don't know why trying to open the config file from within the Options panel by clicking "Open Configuration File" fails, so if someone can shed light on that it would be great.

But apparently I really needed the "server=1" and to set rpcport to some other port that was not already being used for other things...