Home Node Troubleshooting

Home Node Troubleshooting

Home node integrations are in beta, and sometimes things go wrong!

Quick Fixes

Most problems are transient, or can be resolved by restarting the application:

• either uninstall and reinstall Bitfeed from your node platform's app store,
• or, manually restart the Bitfeed server:
  1. Connect to your node via SSH
  2. Restart the Bitfeed Server docker container
     1. On Umbrel, run docker restart bitfeed_api_1
     2. On Citadel, run docker restart bitfeed-api-1

If that doesn't help, refer to the troubleshooting guide below:

Troubleshooting

There are no transactions!

The Bitfeed browser application loads ok, but no transactions appear.

How to diagnose:

1. Check the network status indicator at the top left of the screen (if you can't find this, click the ⚙ icon in the sidebar, and make sure the "Network Status" toggle is set to green):
   1. Network Status indicator is red: go to Server is Offline
   2. Network Status indicator is green: go to Node is Disconnected

Fees are missing or incorrect!

This can happen after a system update or reboot, especially if the mempool is congested. Calculating fees involves looking up and processing a large amount of data, and it can take a while for that data to become available after a reboot.

How to diagnose:

1. Transactions in color by fee rate mode display in orange or dark red, with missing fee data or negative fees.
2. The latest block information shows "Avg Fee Rate: Unavailable"
3. Check your Bitfeed version:
   1. v2.2.0: go to Missing Fees
   2. v2.2.1 or later: just wait, fee data will be restored once the server finishes processing.

Known Issues

Server is Offline

The Bitfeed browser application can't connect to the Bitfeed server.

The application has probably crashed and can't recover - try rebooting your node.

Node is Disconnected

The Bitfeed browser application is connected to the Bitfeed server, but is not receiving new transactions.

---

If your node has been offline recently, or is new and hasn't yet completed the initial block download, Bitfeed will not connect until Bitcoin Core has finished synchronizing the chain.

Check back later.

---

If Bitcoin Core is fully synced, there is a known bug in Bitfeed version v2.1.3 and below (packaged in Umbrel v1.4.13 and v1.4.14) where Bitfeed fails to reestablish connection to Bitcoin Core after an interruption.

Please upgrade your node to the latest version.

If it is not possible to upgrade, restarting Bitfeed should resolve the issue temporarily.

Missing Fees

There is a bug in v2.2.0 where the Bitfeed server can fail to resume processing fee data after becoming overloaded, usually after a system update or reboot when there is significant mempool congestion.

Wait 15-30 minutes for your node to stabilize, then restart Bitfeed.