# Knots 29.3.1 stuck at height 961633 **URL:** \ **Category:** Services Support\ **Created:** [August 11, 2026, 1:18pm UTC](https://community.start9.com/t/knots-29-3-1-stuck-at-height-961633/5568 "2026-08-11T13:18:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![nitro2003](https://community.start9.com/letter_avatar_proxy/v4/letter/n/a698b9/32.png) [@nitro2003](https://community.start9.com/u/nitro2003)\ **Post date:** [August 11, 2026, 1:18pm UTC](https://community.start9.com/t/knots-29-3-1-stuck-at-height-961633/5568/1 "2026-08-11T13:18:30Z")
StartOS 0.4.0, Bitcoin Knots `v29.3.knots20260508` (`#knots:29.3.1:10`), x86 mini PC, non-pruned, txindex + blockfilterindex enabled. Since the 0.4.0 update, the node’s tip is frozen at height 961633 (block dated 2026-08-08). Peers report 961985+. It has never advanced a single block since. `getchaintips` returns only the active tip at 961633 plus old stale forks — **no headers-only entry above the tip**. So this isn’t stalled block download; headers never arrive at all. The log shows, repeatedly: peers connect normally (hundreds cycled through), `Synchronizing blockheaders, height: 961633 (~99.9%)`, then `Timeout downloading headers, disconnecting peer=N` roughly every 15 minutes, and `Potential stale tip detected` counting steadily upward. Ruled out so far: - Clock: `timedatectl` synced, NTP active, matches log UTC - MTU: `ping -M do -s 1472` to a peer succeeds, 20ms, 0% loss - Throughput: 7.5 MB/s HTTP download from the host - Port 8333: TCP connects instantly to peers - Routing: normal LAN gateway, not via any tunnel - Mempool: restarted with `mempool.dat` removed, no change - Tor: set `onlynet` to ipv4+ipv6, SOCKS refusals stopped, sync unchanged Two config details I’m unsure about: `whitebind=0.0.0.0:8333` alongside `bind=0.0.0.0:58333`, and the startup warning that 58333 is shared between Tor and clearnet so localhost connections are denied whitelist permissions. Is that expected for this package? Also seeing `ThreadRPCServer incorrect password attempt from 10.0.3.1` (the LXC bridge gateway) on every start, before and after regenerating RPC credentials. ---
**Author:** ![StuPleb](https://community.start9.com/user_avatar/community.start9.com/stupleb/32/195_2.png) [@StuPleb](https://community.start9.com/u/StuPleb)\ **Post date:** [August 11, 2026, 1:21pm UTC](https://community.start9.com/t/knots-29-3-1-stuck-at-height-961633/5568/2 "2026-08-11T13:21:41Z")
On the Knots/BIP-110 version of Bitcoin (separate, different Bitcoin) you’re on the latest block after the hard fork and the stalling of the separate chain. You’ve done well to avoid all the discussion on this, especially as someone who chose Knots. If you want to sync back to the main/majority Bitcoin chain to continue transacting, you’d either have to run the pre-RDTS version of Knots, or switch to Bitcoin Core. ---
**Author:** ![Rexter](https://community.start9.com/user_avatar/community.start9.com/rexter/32/371_2.png) [@Rexter](https://community.start9.com/u/Rexter)\ **Post date:** [August 11, 2026, 6:21pm UTC](https://community.start9.com/t/knots-29-3-1-stuck-at-height-961633/5568/3 "2026-08-11T18:21:02Z")
This is the current state of the two chains, at the time of this post: ![state1](https://community.start9.com/uploads/default/original/2X/6/66b20facc58c4743ed47454283730b07bce5f00a.png) ---
**Author:** ![nitro2003](https://community.start9.com/letter_avatar_proxy/v4/letter/n/a698b9/32.png) [@nitro2003](https://community.start9.com/u/nitro2003)\ **Post date:** [August 12, 2026, 9:27am UTC](https://community.start9.com/t/knots-29-3-1-stuck-at-height-961633/5568/4 "2026-08-12T09:27:54Z")
thank you everyone. Switched to preRDTS, all is fine now ---
**Author:** ![system](https://community.start9.com/uploads/default/original/1X/2dcde8aa6ad3ce3d7873096ee4b3e5395e19a7b5.png) [@system](https://community.start9.com/u/system)\ **Post date:** [August 14, 2026, 9:28am UTC](https://community.start9.com/t/knots-29-3-1-stuck-at-height-961633/5568/5 "2026-08-14T09:28:01Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.