1. Get-started

1. Install consensus client.
2. Start besu.

besu --network=sepolia --rpc-http-enabled=true --rpc-http-host=0.0.0.0 --rpc-http-cors-origins="*" --rpc-ws-enabled=true --rpc-ws-host=0.0.0.0 --host-allowlist="*" --engine-host-allowlist="*" --engine-rpc-enabled --engine-jwt-secret="jwtsecret.hex" --data-path=/home/ec2-user/besu-testnet-sepolia

1. Start teku.

teku --network=sepolia --ee-endpoint=http://localhost:8551 --ee-jwt-secret-file=jwtsecret.hex --metrics-enabled=true --ignore-weak-subjectivity-period-enabled --checkpoint-sync-url=https://beaconstate-sepolia.chainsafe.io

1. Syncing besu and teku and importing block.

2. Resolved problem

1. Not connect between teku and besu on sepolia testnet

   • snapshot

   • solution: --data-path={absolute path}

   • causes

     Without knowing more about your setup I can't tell you why that worked 🙂
     It was just a hunch, I'm not sure it's a requirement but absolute paths are generally a good idea if you're wanting to run any besu (or any process) as a service for example...likely don't want your data directory to be the same location as the besu binary.
     Maybe what happened is the jwt file was created automatically by besu in an unexpected location due to data-path misconfiguration and the auto-generated one didn't match the name your provided (jwt.hex vs jwtsecret.hex)?
     

Reference

hyperledger-get-started