Besu and Teku do not synchronize themselves

[lucianoacsilva]

Hello,

I am trying to run a Ethereum Sepolia testnet beacon node on my machine, using Besu as execution client and Teku as consensus client. I create the JWT secret for communication between themselves, and referenced it in their configuration clients. However, when I run up both of them, Teku complains that is waiting for execution client to synchronize eternally (despite it can reach Besu). What could be happening?

Grateful for all the possible help

Luciano

Steps to Reproduce

1. Start Besu with configuration file (besu --config-file=config.toml).
2. Start Teku with configuration file (teku --config-file=config.yaml).

Expected behavior: Execution and consensus client sinchronize.

Actual behavior: They do not sinchronize.

Frequency: Always

Logs

Versions (Add all that apply)

• Software version: 25.11.0
• Java version: 21.0.9
• OS Name & Version: Oracle Linux Server 9.7
• Kernel Version: 5.14.0-611.9.1.el9_7.x86_64
• Cloud VM, type, size: Azure
• Consensus Client & Version if using Proof of Stake: Teku 25.11.1

Additional Information (Add any of the following or anything else that may be relevant)

Teku configuration file:

Besu configuration file:

[macfarla]

From your logs, teku has zero peers. One thing to check is networking - there may be some helpful tips in this troubleshooting doc from Besu https://besu.hyperledger.org/public-networks/how-to/troubleshoot/peering

If you can share besu logs, that might have extra info as well

[jflo]

@lucianoacsilva you can take this to discord for faster, more synchronous support