I'll check the error message and report back

Reply to this note

Please Login to reply.

Discussion

Failed to connect, connection refused. Recently updated raspiblitz, did not have this problem before

Head to a terminal session on the device.

systemctl status electrs.service

Is it running?

Activating (auto-restart) (result: exit code)

Code=exited, status=1/FAILURE

Well hey, look at that, found the problem

It gives you a command to run in that output somewhere. Sudo journalctl -u electrs.service I think. Run it. Gives you more log details.

Will check, ty

Bitcoin p2p failed to connect on local port 8333

Connection refused (os error 111)

Continues to restart with exit code and failure to connect

Check if bitcoind is running.

Systemctl status bitcoind

Affirmative, has been running for the past month

Soooo I don’t run electrum myself, I’d need to look the specifics up. But, broadly speaking, perms issue? Connection refused to me means its authentication attempt was tried and rejected.

Check your bitcoin conf file (file location noted in the service status output) to make sure it’s in server mode or has something else along those lines for electrum to communicate through. Then electrum probably has a conf file (that should also be noted in its status output) that needs some settings confirmed as well.

Appreciate your feedback , I'll jump on it when I am able to 🤙🏻