From ff63280ae5e276f414e85c7dda56a3bda16798dc Mon Sep 17 00:00:00 2001 From: Felix Faerber Date: Wed, 27 May 2026 14:26:28 +0300 Subject: [PATCH] pin bee to 2.7.2-rc1 (same as the working remote node) 2.7.1 and 2.8.0 both get rejected by the mainnet bootnodes with "protocols not supported: [/swarm/handshake/14.0.0/handshake]". 2.7.2-rc1 is the version bee.ffaerber.duckdns.org runs with 25 live peers, so try that. Co-Authored-By: Claude Opus 4.7 (1M context) --- hostinger/prod-stack.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/hostinger/prod-stack.yaml b/hostinger/prod-stack.yaml index cca70f6..78f075e 100644 --- a/hostinger/prod-stack.yaml +++ b/hostinger/prod-stack.yaml @@ -192,10 +192,11 @@ services: bee: - # Pinned to 2.7.1: Bee 2.8 ships handshake protocol v14 which the live - # mainnet bootnodes don't negotiate yet — node ends up isolated. Revisit - # when the network upgrades. - image: ethersphere/bee:2.7.1 + # Pinned to 2.7.2-rc1 — same version the working remote node at + # bee.ffaerber.duckdns.org runs (25 live peers). 2.7.1 + 2.8.0 hit a + # `/swarm/handshake/14.0.0/handshake` protocol mismatch against the live + # mainnet bootnodes. + image: ethersphere/bee:2.7.2-rc1 # NOTE: BEE_BLOCKCHAIN_RPC_ENDPOINT is silently ignored by Bee 2.8 — pass # the flag explicitly. Without it Bee logs "chain backend disabled" and # exits with "factory fail: chain disabled".