Stopped syncing with the mainnet (Isthmus)

[pavelush]

I see such errors after the Isthmus update (op-node).
t=2025-05-15T19:12:24+0000 lvl=error msg="Error initializing the rollup node" err="failed to init the runtime config: failed to load runtime configuration repeatedly, last error: operation failed permanently after 5 attempts: failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x42ed5b6bd94ac6e79aa725a6a3714a0ac1fcda220ab2f83135bb51fca0818614: hash sort failed: loadIntoTable : subTrieRoot(00c31f2e281a952ccb70fa53694ca6526a1a68e8492ea4c06cf28a99fda90406) != cellHash(5a939138d72103c156f462d70b390e558fd34c77f206cb178c1d73aba4b16681)"

The node-execution-client writes:

t=2025-05-15T19:14:44+0000 lvl=info msg="Looking for peers" peercount=34 tried=75 static=0
t=2025-05-15T19:14:55+0000 lvl=info msg="Looking for peers" peercount=34 tried=55 static=0
t=2025-05-15T19:15:05+0000 lvl=info msg="Looking for peers" peercount=34 tried=64 static=0
t=2025-05-15T19:15:16+0000 lvl=info msg="Looking for peers" peercount=34 tried=84 static=0
t=2025-05-15T19:15:27+0000 lvl=info msg="Looking for peers" peercount=34 tried=33 static=0
t=2025-05-15T19:15:37+0000 lvl=info msg="Looking for peers" peercount=34 tried=18 static=0
t=2025-05-15T19:15:48+0000 lvl=info msg="Looking for peers" peercount=34 tried=74 static=0
t=2025-05-15T19:15:58+0000 lvl=info msg="Looking for peers" peercount=34 tried=72 static=0
t=2025-05-15T19:16:08+0000 lvl=info msg="Looking for peers" peercount=34 tried=50 static=0
t=2025-05-15T19:16:18+0000 lvl=info msg="Looking for peers" peercount=34 tried=51 static=0
t=2025-05-15T19:16:32+0000 lvl=info msg="Looking for peers" peercount=34 tried=42 static=0
t=2025-05-15T19:16:42+0000 lvl=info msg="Looking for peers" peercount=34 tried=59 static=0
t=2025-05-15T19:16:53+0000 lvl=info msg="Looking for peers" peercount=34 tried=37 static=0
t=2025-05-15T19:17:05+0000 lvl=info msg="Looking for peers" peercount=34 tried=52 static=0
t=2025-05-15T19:17:15+0000 lvl=info msg="Looking for peers" peercount=34 tried=44 static=0
t=2025-05-15T19:17:25+0000 lvl=info msg="Looking for peers" peercount=34 tried=57 static=0
t=2025-05-15T19:17:36+0000 lvl=info msg="Looking for peers" peercount=34 tried=57 static=0
t=2025-05-15T19:17:47+0000 lvl=info msg="Looking for peers" peercount=34 tried=47 static=0
t=2025-05-15T19:17:59+0000 lvl=info msg="Looking for peers" peercount=34 tried=79 static=0

But sometimes it tries to connect and it doesn't work.
t=2025-05-15T19:18:00+0000 lvl=warn msg="Served eth_coinbase" conn=100.60.200.00:45722 reqid=2 duration=47.368µs err="the method eth_coinbase **does not exist/is not available**"

[pavelush]

Solved: it was necessary to replace the BEACON RPC, publicnode does not work.

[lemarcque]

Also resolved by changing both L1 execution client and L1 Beacon RPC.

[Viktoriabth]

Also resolved by changing both L1 execution client and L1 Beacon RPC.

Could you please tell me what links you replaced them with? To your APIs? What services did you use?
For example, https://developer.metamask.io/ gives only one key, it will not work for L1 Beacon and L1 execution.

[pavelush]

Also resolved by changing both L1 execution client and L1 Beacon RPC.

Could you please tell me what links you replaced them with? To your APIs? What services did you use? For example, https://developer.metamask.io/ gives only one key, it will not work for L1 Beacon and L1 execution.

I used chainstack rpc on a free tariff. Everything is working.

[rdin777]

Update/Workaround using Chainstack RPC

I can confirm that I was able to successfully run and sync my Unichain node by configuring it to use a Chainstack RPC endpoint (Free Tier). The node is currently running without synchronization issues.

This suggests that the "Stopped syncing" problem might be related to the reliability, stability, or network path to certain public/free RPC endpoints, rather than a bug in the core unichain-node software itself.

If other users are experiencing this intermittent synchronization failure, testing with a dedicated RPC provider like Chainstack or Alchemy might help diagnose whether the issue is network-related.