/home/bitcoin/.bitcoin permissions vs. /data/bitcoin about raspibolt

[BillyMabe456]

All I know is I've had issues with these cookie permissions for a few months now, not sure what is going on exactly but something changed after upgrading to bitcoin 25.0 I've been running this node for several years and try to keep up with the changes. My power goes out occasionally or my router freaks out, and my node needs to be restarted. When it does it generates the cookie file with the wrong permissions: ( -rw------- ) and nothing can access it.

There's code in the bitcoind.service that is supposed to assign the correct permissions to this cookie on startup which doesn't seem to work (probably lacking the correct permissions somehow)
"-startupnotify="chmod g+r /home/bitcoin/.bitcoin/.cookie"

I found if I switch to the bitcoin user, then run "chmod g+r /home/bitcoin/.bitcoin/.cookie" myself, All my RPC connections like electrum or whatever work again.

Unfortunately, that's as far as my troubleshooting could take me.

[jpanachida]

As I understand the issue, it is not about .cookie permission but the absolute path of it. Members of bitcoin group (e.g. admin, electrs) should access datadir using /data/bitcoin/ or ~/.bitcoin/ path (if defined). They should not use bitcoin's home directory /home/bitcoin/ because of insufficient permissions.

[dosoid]

I had the same issue, "Permission denied", even that .cookie file has group "read" access to bitcoin group....change electrs.conf file daemon_dir to /data/bitcoin, now it's working...

[willcl-ark]

There were some permissions changes merged in bitcoin/bitcoin#17127 which mean that the cookie will be created with 0700 permissions, i.e. only readable by the user (bitcoin for you, I think?). Currently, this can't be configured at the Bitcoin Core level, requiring the -startupnotify workaround described above.

However, I have a PR open here: bitcoin/bitcoin#28167 which aims to permit setting permissions on the .cookie file, for use-cases such as this. With that patch you'd be able to add e.g. -rpccookieperms=640 to your startup options.

[github-actions]

This issue is marked as stale because there was no activity for 60 days. If the issue stays inactive, it will be closed in a week.

[github-actions]

This issue has been closed due to inactivity.