- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
2.1 KiB
2.1 KiB
Besu RPC All Fixes Complete
Date: 2026-01-03
Status: ✅ ALL FIXES APPLIED
Summary
Applied comprehensive fixes to all RPC nodes to resolve configuration issues and enable proper RPC access.
Fixes Applied
1. Host Allowlist Restrictions (VMID 2400, 2501, 2502)
- Issue: RPC endpoints returning "Host not authorized"
- Root Cause: Besu requires explicit
rpc-http-host-allowlistconfiguration for external access - Fix: Added
rpc-http-host-allowlist=["*"]to config files - Config Files Updated:
- VMID 2400:
/etc/besu/config-rpc-thirdweb.toml - VMID 2501:
/etc/besu/config-rpc-public.toml - VMID 2502:
/etc/besu/config-rpc-public.toml
- VMID 2400:
2. Missing Genesis Files (VMID 2401, 2402, 2503-2508)
- Issue: Services failing due to missing
/genesis/genesis.json - Fix: Copied
genesis.jsonandstatic-nodes.jsonfrom working node (VMID 2500) - Files Copied:
/genesis/genesis.json/genesis/static-nodes.json
3. Fast Sync Configuration Error (VMID 2401, 2402)
- Issue:
--fast-sync-min-peers can't be used with FULL sync-mode - Fix: Removed
fast-sync-min-peersoption from config files - Config File:
/etc/besu/config-rpc-thirdweb.toml
4. Permissions File Path (VMID 2503-2508)
- Issue: Services looking for
/etc/besu/permissions-nodes.tomlbut file was in/permissions/permissions-nodes.toml - Fix: Copied permissions file to
/etc/besu/permissions-nodes.tomlon all affected nodes
Configuration Changes
Host Allowlist
Added to all affected config files:
rpc-http-host-allowlist=["*"]
This allows external connections to the RPC endpoints.
Services Status
After fixes:
- ✅ All services restarted
- ⏳ Services initializing (may need time to fully start)
- ✅ Configuration files updated
- ✅ Missing files copied
Next Steps
- ✅ All fixes applied
- ⏳ Wait for services to fully start (1-2 minutes)
- ⏳ Verify all RPC endpoints are responding
- ⏳ Check block synchronization status
Last Updated: 2026-01-03