# Bitcoin Node stuck on "Starting" **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [July 2, 2023, 7:23pm UTC](https://community.umbrel.com/t/bitcoin-node-stuck-on-starting/12956 "2023-07-02T19:23:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![SHUTTEHFACE](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/shuttehface/32/1431_2.png) [@SHUTTEHFACE](https://community.umbrel.com/u/SHUTTEHFACE)\ **Post date:** [July 2, 2023, 7:23pm UTC](https://community.umbrel.com/t/bitcoin-node-stuck-on-starting/12956/1 "2023-07-02T19:23:04Z")
Hi, I updated to the most recent Umbrel update but am having issues with my Bitcoin node stuck on “Starting”. I’ve tried restarting a couple times but no luck. Here are the logs, appreciate any help! ```auto bitcoin Attaching to bitcoin_server_1, bitcoin_tor_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_i2pd_daemon_1, bitcoin_tor_server_1 bitcoind_1 | 2023-07-02T19:15:32Z Using wallet /data/.bitcoin/wallet.dat bitcoind_1 | 2023-07-02T19:15:32Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/database ErrorFile=/data/.bitcoin/db.log bitcoind_1 | 2023-07-02T19:15:32Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) bitcoind_1 | 2023-07-02T19:15:32Z Using wallet /data/.bitcoin/jam_default/wallet.dat bitcoind_1 | 2023-07-02T19:15:32Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/jam_default/database ErrorFile=/data/.bitcoin/jam_default/db.log bitcoind_1 | 2023-07-02T19:15:32Z Using /16 prefix for IP bucketing bitcoind_1 | 2023-07-02T19:15:32Z init message: Loading P2P addresses… bitcoind_1 | 2023-07-02T19:15:36Z Error: Invalid or corrupt peers.dat (Checksum mismatch, data corrupted). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/data/.bitcoin/peers.dat") out of the way (rename, move, or delete) to have a new one created on the next start. bitcoind_1 | Error: Invalid or corrupt peers.dat (Checksum mismatch, data corrupted). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/data/.bitcoin/peers.dat") out of the way (rename, move, or delete) to have a new one created on the next start. bitcoind_1 | 2023-07-02T19:15:36Z Shutdown: In progress... server_1 | umbrel-middleware server_1 | ::ffff:10.21.0.45 - - [Sun, 02 Jul 2023 19:15:32 GMT] "GET /v1/bitcoind/info/status HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0" server_1 | server_1 | umbrel-middleware server_1 | ::ffff:10.21.0.45 - - [Sun, 02 Jul 2023 19:15:34 GMT] "GET /v1/bitcoind/info/status HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0" server_1 | server_1 | umbrel-middleware server_1 | ::ffff:10.21.0.45 - - [Sun, 02 Jul 2023 19:15:36 GMT] "GET /v1/bitcoind/info/status HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0" server_1 | server_1 | umbrel-middleware tor_1 | Jul 02 08:44:25.000 [notice] No circuits are opened. Relaxed timeout for circuit 578 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 8820 seconds] tor_1 | Jul 02 12:04:07.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 20 circuits open. I've sent 11.25 MB and received 18.15 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 15 connections with IPv4 and 0 with IPv6. tor_1 | Jul 02 12:04:07.000 [notice] While bootstrapping, fetched this many bytes: 633939 (consensus network-status fetch); 11094 (authority cert fetch); 8388658 (microdescriptor fetch) tor_1 | Jul 02 12:04:07.000 [notice] While not bootstrapping, fetched this many bytes: 330967 (consensus network-status fetch); 17474 (authority cert fetch); 1113522 (microdescriptor fetch) tor_1 | Jul 02 13:04:35.000 [notice] No circuits are opened. Relaxed timeout for circuit 849 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 15660 seconds] tor_1 | Jul 02 18:04:07.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 31 circuits open. I've sent 15.50 MB and received 21.59 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 16 connections with IPv4 and 0 with IPv6. tor_1 | Jul 02 18:04:07.000 [notice] While bootstrapping, fetched this many bytes: 633939 (consensus network-status fetch); 11094 (authority cert fetch); 8388658 (microdescriptor fetch) tor_1 | Jul 02 18:04:07.000 [notice] While not bootstrapping, fetched this many bytes: 467680 (consensus network-status fetch); 22802 (authority cert fetch); 1146279 (microdescriptor fetch) app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... app_proxy_1 | Validating token: 703f794cba83 ... i2pd_daemon_1 | 18:59:29@885/error - Tunnels: Can't select next hop for tpMdOb-eqm9kz3oaqG6aZord66du9~XgEtwzybMekyo= i2pd_daemon_1 | 18:59:29@885/error - Tunnels: Can't create inbound tunnel, no peers available i2pd_daemon_1 | 19:00:14@885/error - Tunnels: Can't select next hop for wtoKX6F2Z2K~USWY2qQwM-iUYZ4PPKf5HIgNsL1CwA0= i2pd_daemon_1 | 19:00:14@885/error - Tunnels: Can't create inbound tunnel, no peers available i2pd_daemon_1 | 19:02:00@885/error - Tunnel: Tunnel with id 526436985 already exists i2pd_daemon_1 | 19:10:25@311/error - NetDb: jZUfLzSXZXBmi6RmzepxP3BesqZO1CG6pkSKodXLd3k= destination requested, but no tunnels found i2pd_daemon_1 | 19:10:33@796/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message i2pd_daemon_1 | 19:11:29@885/error - Tunnels: Can't select next hop for 1-UVSh2f1pNZy9ao232tlECm69NiWw1foH4ow1JLdsM= i2pd_daemon_1 | 19:11:29@885/error - Tunnels: Can't create inbound tunnel, no peers available i2pd_daemon_1 | 19:13:34@991/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message ``` ---
**Author:** ![SHUTTEHFACE](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/shuttehface/32/1431_2.png) [@SHUTTEHFACE](https://community.umbrel.com/u/SHUTTEHFACE)\ **Post date:** [July 2, 2023, 8:05pm UTC](https://community.umbrel.com/t/bitcoin-node-stuck-on-starting/12956/2 "2023-07-02T20:05:37Z")
deleted peers.dat worked for me [Error: Invalid or corrupt peers.dat file](https://community.umbrel.com/t/error-invalid-or-corrupt-peers-dat-file/9382/14) ---
**Author:** ![my\_bitcoin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/my_bitcoin/32/5762_2.png) [@my\_bitcoin](https://community.umbrel.com/u/my_bitcoin)\ **Post date:** [July 3, 2023, 2:05am UTC](https://community.umbrel.com/t/bitcoin-node-stuck-on-starting/12956/3 "2023-07-03T02:05:12Z")
that is what happens when its not shut down properly. It is safe to delete that fine and it will usually restore your node when its been shutdown improperly ---
**Author:** ![gteam84](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gteam84](https://community.umbrel.com/u/gteam84)\ **Post date:** [July 3, 2023, 2:25pm UTC](https://community.umbrel.com/t/bitcoin-node-stuck-on-starting/12956/4 "2023-07-03T14:25:32Z")
having this same issue since updating to 0.5.4 and btc 25. Bitcoin node stuck on starting. I’ve refreshed and restarted, still stuck on starting ---
**Author:** ![gteam84](https://avatars.discourse-cdn.com/v4/letter/g/b3f665/32.png) [@gteam84](https://community.umbrel.com/u/gteam84)\ **Post date:** [July 3, 2023, 2:40pm UTC](https://community.umbrel.com/t/bitcoin-node-stuck-on-starting/12956/5 "2023-07-03T14:40:31Z")
I have updated to 0.5.4 and bitcoin 25 bitcoin Attaching to bitcoin\_server\_1, bitcoin\_tor\_server\_1, bitcoin\_i2pd\_daemon\_1, bitcoin\_bitcoind\_1, bitcoin\_tor\_1, bitcoin\_app\_proxy\_1 app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | [HPM] Error occurred while proxying request umbrel.local:2100/v1/bitcoind/info/status to [http://10.21.22.2:3005/](http://10.21.22.2:3005/) [ECONNRESET] ([Errors | Node.js v20.3.1 Documentation](https://nodejs.org/api/errors.html#errors_common_system_errors)) app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | [HPM] Error occurred while proxying request umbrel.local:2100/v1/bitcoind/info/status to [http://10.21.22.2:3005/](http://10.21.22.2:3005/) [ECONNRESET] ([Errors | Node.js v20.3.1 Documentation](https://nodejs.org/api/errors.html#errors_common_system_errors)) app\_proxy\_1 | Validating token: 9fa4d68f15f8 … app\_proxy\_1 | Validating token: 9fa4d68f15f8 … i2pd\_daemon\_1 | 14:21:30@515/error - Tunnels: Can’t select next hop for vgHvtO-nSmpBsOz3ip8FZZLaTAMR38UP5XNnocTe~eg= i2pd\_daemon\_1 | 14:21:30@515/error - Tunnels: Can’t create inbound tunnel, no peers available i2pd\_daemon\_1 | 14:21:30@515/error - Tunnels: Can’t select next hop for vgHvtO-nSmpBsOz3ip8FZZLaTAMR38UP5XNnocTe~eg= i2pd\_daemon\_1 | 14:21:30@515/error - Tunnels: Can’t create inbound tunnel, no peers available i2pd\_daemon\_1 | 14:21:45@515/error - Tunnels: Can’t select next hop for IxKMHWDtIq35CZInPQhYYod2BQG~odh~6yBFXCYl~-o= i2pd\_daemon\_1 | 14:21:45@515/error - Tunnels: Can’t create inbound tunnel, no peers available i2pd\_daemon\_1 | 14:21:59@515/error - Tunnels: Can’t select next hop for WMOHOp~hHzLo7NRBQyQ5QYR3kcdAtkaTNudlBSdowVc= i2pd\_daemon\_1 | 14:21:59@515/error - Tunnels: Can’t create inbound tunnel, no peers available i2pd\_daemon\_1 | 14:26:14@515/error - Tunnels: Can’t select next hop for YchUPLht7sUNOxszacNdmKTIL~~SU2~IUBT0QpRFfZs= i2pd\_daemon\_1 | 14:26:14@515/error - Tunnels: Can’t create inbound tunnel, no peers available bitcoind\_1 | Error: Settings file could not be read: bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json bitcoind\_1 | Error: Settings file could not be read: bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json bitcoind\_1 | Error: Settings file could not be read: bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json bitcoind\_1 | Error: Settings file could not be read: bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json bitcoind\_1 | Error: Settings file could not be read: bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json