Can't use bitcoin-cli unless restart about raspibolt

[johnny-cash]

The issue with "After=network.target" is solved change in raspi-config the boot options to wait for network at boot.

"After=network.target" + "Wait for network at boot" in raspi-config -> work 100%

[robclark56]

Good news. Thanks team.

Making these 2 changes fixed the problem

• Updating getpublicip.service with "After=network.target"

• "Wait for network at boot" in raspi-config

BONUS
It also solved a related issue with lnd not starting with an externalip
BEFORE
systemctl status lnd
/usr/local/bin/lnd --externalip=

AFTER
systemctl status lnd
/usr/local/bin/lnd --externalip=AAA.BBB.CCC.DDD <--- my external IP

:-)

[robclark56]

PS ... Absolutely GREAT guide by the way!

Thanks

[Stadicus]

What's your output of sudo netstat -nap|grep bitcoin|grep LISTEN?

[johnny-cash]

In service getpublicip

Change

After=network.target

[Stadicus]

I changed this setting as there is a known issue with the "After=network.target" that would result in exactly this. If you run sudo netstat -nap|grep bitcoin|grep LISTEN, you should see tcp bound to both ports :8332 and :8333 (either on ip 127.0.0.1 or 0.0.0.0).

If the suggestion above does not work, try the setting After=multi-user.target in getpublicip.service.

[Stadicus]

I for myself never had this issue, I am not sure when this happens as I cannot reproduce it. @robclark56, your feedback on the above options would be very helpful.

[Stadicus]

"After=network.target" + "Wait for network at boot" in raspi-config

I think, the combination provided by @johnny-cash is the most robust one. I included it in the guide.