# Nodes on v1.7.14-0-g22769b30 causes errors and running into outOfSync

**URL:** <https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098>\
**Category:** Validators\
**Created:** [November 4, 2025, 9:00pm UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098 "2025-11-04T21:00:00Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zeferot](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/zeferot/32/626_2.png) [@Zeferot](https://forum.klever.org/u/Zeferot)\
**Post date:** [November 4, 2025, 9:00pm UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/1 "2025-11-04T21:00:01Z")

</div>

today our nodes got many errors in log and went OutOfSync state what can cause this behavior?

EDIT: my node is again in sync after updating to v1.7.15-0-gc1de9106 so being on the old version can causes errors. Nvm after updated the same problem most nodes went OutOfSync, most of it happend during the epoch shift

[@Validators](https://forum.klever.org/groups/validators) you experience the same?

 ![2025-11-05 00_03_55-error](https://europe1.discourse-cdn.com/flex013/uploads/klever/original/2X/c/cb76cc70a10518cfdccbc01e98bf9c511e9fd03f.jpeg)

---

<div class="post-metadata">

**Author:** ![Maik](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/maik/32/33_2.png) [@Maik](https://forum.klever.org/u/Maik)\
**Post date:** [November 5, 2025, 7:16am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/2 "2025-11-05T07:16:36Z")

</div>

The team is already checking, seems like the old version should be updated asap by all Validator runners.

> [@Klever Blockchain v1.7.15 – Performance Update Now Live!](https://forum.klever.org/t/klever-blockchain-v1-7-15-performance-update-now-live/4096):
>
> [image] Dear [@Validators](https://forum.klever.org/groups/validators) , We’re excited to announce the release of Klever Blockchain v1.7.15, now live on Mainnet! This version delivers major performance enhancements, particularly in smart contract execution, as well as key security and infrastructure updates that make your node operations faster, safer, and more reliable. Unlike previous releases, this is not a mandatory upgrade, but it is highly recommended to benefit from the latest optimizations and stability improvements. …

---

<div class="post-metadata">

**Author:** ![albin.nowak](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@albin.nowak](https://forum.klever.org/u/albin.nowak)\
**Post date:** [November 5, 2025, 7:38am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/3 "2025-11-05T07:38:07Z")

</div>

> [@Zeferot](#):
>
> v1.7.15-0-gc1de9106

Hi Klever Team, could you please answer? Most of the nodes are jailed

---

<div class="post-metadata">

**Author:** ![albin.nowak](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@albin.nowak](https://forum.klever.org/u/albin.nowak)\
**Post date:** [November 5, 2025, 7:44am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/4 "2025-11-05T07:44:13Z")

</div>

It doesn’t help.  
I updated my node but it still keeps losing blocks

---

<div class="post-metadata">

**Author:** ![janill](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/janill/32/187_2.png) [@janill](https://forum.klever.org/u/janill)\
**Post date:** [November 5, 2025, 7:47am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/5 "2025-11-05T07:47:46Z")

</div>

The new version seems to help, but it is still unstable. My nodes still lose blocks from time to time.

---

<div class="post-metadata">

**Author:** ![Zeferot](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/zeferot/32/626_2.png) [@Zeferot](https://forum.klever.org/u/Zeferot)\
**Post date:** [November 5, 2025, 7:55am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/6 "2025-11-05T07:55:17Z")

</div>

Best part is when you have a full fallback setting and you stil got rekt

 ![grafik](https://europe1.discourse-cdn.com/flex013/uploads/klever/original/2X/c/c4fc79988fe31e92c406e821d6617cb8d9a0cfe5.png)

---

<div class="post-metadata">

**Author:** ![Maik](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/maik/32/33_2.png) [@Maik](https://forum.klever.org/u/Maik)\
**Post date:** [November 5, 2025, 9:05am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/7 "2025-11-05T09:05:24Z")

</div>

as long as you have updated all nodes to the very latest version, you are fine.

once all nodes are updated everything will get fine again.

---

<div class="post-metadata">

**Author:** ![fbsobreira](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/fbsobreira/32/490_2.png) [@fbsobreira](https://forum.klever.org/u/fbsobreira)\
**Post date:** [November 5, 2025, 9:14am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/8 "2025-11-05T09:14:14Z")

</div>

Seeing the same behavior. Root cause is a **mixed-version** set: some validators on **v1.7.15** (faster KVM / tighter timeouts) and others on **v1.7.14**. With **\>25%** of consensus still on 1.7.14, those slower nodes were timing out on a specific tx path and **rejecting** it, while the 1.7.15 nodes **accepted** it. That split caused prevote/precommit churn, **outOfSync** on 1.7.14, and consensus instability (blocks proposed then bounced).

**Fix:** upgrade all validators to **v1.7.15** and ensure **primary + fallback run the exact same version**. Don’t mix versions.

---

<div class="post-metadata">

**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\
**Post date:** [November 5, 2025, 9:33am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/9 "2025-11-05T09:33:57Z")

</div>

It is weird as KUNAIKASH-4 shows fallback at 1.7.14, but it is running on 1.7.15 and still got jailed even with no mixed versions. I have checked all logs and bot mainnode and fallback runs on 1.7.15

---

<div class="post-metadata">

**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\
**Post date:** [November 5, 2025, 9:54am UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/10 "2025-11-05T09:54:51Z")

</div>

Not totally true, even @CryptoJaeger had updated all nodes and have some jailed on the newest version so there is more on going

---

<div class="post-metadata">

**Author:** ![albin.nowak](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@albin.nowak](https://forum.klever.org/u/albin.nowak)\
**Post date:** [November 5, 2025, 1:07pm UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/11 "2025-11-05T13:07:16Z")

</div>

Guys, do you have any updates? The problem is still here.

---

<div class="post-metadata">

**Author:** ![MathijsBok](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/mathijsbok/32/3_2.png) [@MathijsBok](https://forum.klever.org/u/MathijsBok)\
**Post date:** [November 5, 2025, 1:07pm UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/12 "2025-11-05T13:07:38Z")

</div>

What problem do you face, can you show?

---

<div class="post-metadata">

**Author:** ![janill](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.klever.org/janill/32/187_2.png) [@janill](https://forum.klever.org/u/janill)\
**Post date:** [November 5, 2025, 1:51pm UTC](https://forum.klever.org/t/nodes-on-v1-7-14-0-g22769b30-causes-errors-and-running-into-outofsync/4098/13 "2025-11-05T13:51:10Z")

</div>

Nodes are periodically running out of sync, even on the latest version.
