Files
proxmox/reports/status/BESU_RPC_FIXES_APPLIED.md
defiQUG cb47cce074 Complete markdown files cleanup and organization
- 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.
2026-01-06 01:46:25 -08:00

52 lines
1.7 KiB
Markdown

# Besu RPC Fixes Applied
**Date**: 2026-01-03
**Status**: ✅ **FIXES APPLIED**
---
## Issues Fixed
### 1. Host Allowlist Restrictions (VMID 2400, 2501, 2502)
- **Issue**: RPC endpoints returning "Host not authorized"
- **Fix**: Removed `rpc-http-host-allowlist` and `rpc-ws-origins` from config files
- **Config Files**:
- VMID 2400: `/etc/besu/config-rpc-thirdweb.toml`
- VMID 2501: `/etc/besu/config-rpc-public.toml`
- VMID 2502: `/etc/besu/config-rpc-public.toml`
### 2. Missing Genesis Files (VMID 2401, 2402, 2503-2508)
- **Issue**: Services failing due to missing `/genesis/genesis.json`
- **Fix**: Copied `genesis.json` from working node (VMID 2500) to all affected nodes
- **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-peers` option 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.toml` but file was in `/permissions/permissions-nodes.toml`
- **Fix**: Copied permissions file to `/etc/besu/permissions-nodes.toml` on all affected nodes
---
## Actions Taken
1. ✅ Removed host allowlist restrictions from config files
2. ✅ Copied missing genesis files to all nodes
3. ✅ Fixed fast-sync configuration errors
4. ✅ Fixed permissions file paths
5. ✅ Restarted all services
6. ✅ Verified RPC endpoints
---
## Current Status
After fixes, services have been restarted and are initializing. Some nodes may need additional time to fully start and sync.
---
**Last Updated**: 2026-01-03