Files
proxmox/reports/status/BESU_RPC_STATUS_FINAL.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

97 lines
3.0 KiB
Markdown

# Besu RPC Status Check - Final Results
**Date**: 2026-01-03
**Nodes Checked**: All 12 RPC nodes (VMID 2400-2402, 2500-2508)
---
## Summary
| Status | Count | VMIDs |
|--------|-------|-------|
| ✅ Working (Chain 138) | 1/12 | 2500 |
| ⚠️ Host not authorized | 3/12 | 2400, 2501, 2502 |
| ❌ Not responding | 8/12 | 2401, 2402, 2503-2508 |
---
## Detailed Results
### ✅ Working (1 node)
**VMID 2500** (192.168.11.250)
- ✅ Chain ID: 138
- ✅ Block Number: 0x89de6 (564,646 in decimal)
- ✅ RPC responding correctly
- ✅ Service status: active
### ⚠️ Host Not Authorized (3 nodes)
These nodes are running but have RPC host allowlist restrictions configured:
- **VMID 2400** (192.168.11.240): Service active, RPC host allowlist configured
- **VMID 2501** (192.168.11.251): Service active, RPC host allowlist configured
- **VMID 2502** (192.168.11.252): Service active, RPC host allowlist configured
**Note**: These nodes are functioning but require proper Host header or host allowlist configuration to accept external connections. They respond correctly from localhost.
### ❌ Not Responding (8 nodes)
These nodes are either starting up or have configuration issues:
- **VMID 2401** (192.168.11.241): Service activating
- **VMID 2402** (192.168.11.242): Service active but RPC not responding
- **VMID 2503** (192.168.11.253): Service active but RPC not responding
- **VMID 2504** (192.168.11.254): Service activating
- **VMID 2505** (192.168.11.201): Service activating
- **VMID 2506** (192.168.11.202): Service activating
- **VMID 2507** (192.168.11.203): Service activating
- **VMID 2508** (192.168.11.204): Service active but RPC not responding
---
## Test Results
### VMID 2500 (Working Example)
```bash
# Chain ID
curl -X POST -H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":1}' \
http://192.168.11.250:8545
# Response: {"jsonrpc":"2.0","id":1,"result":"138"}
# Block Number
curl -X POST -H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' \
http://192.168.11.250:8545
# Response: {"jsonrpc":"2.0","id":1,"result":"0x89de6"}
```
### VMID 2400, 2501, 2502 (Host Not Authorized)
```bash
# Response: {"message":"Host not authorized."}
```
This indicates RPC host allowlist is configured and needs to be updated or Host header needs to match allowed hosts.
---
## Recommendations
1. **Host Allowlist Nodes** (2400, 2501, 2502):
- Review RPC host allowlist configuration if external access is needed
- Check `rpc-http-host-allowlist` setting in Besu config files
- Update allowlist or remove restriction if external access is required
2. **Non-Responding Nodes** (2401, 2402, 2503-2508):
- Check service logs: `journalctl -u besu-rpc -f`
- Verify configuration files are correct
- Ensure services have completed startup (some are still activating)
- Check for port binding issues or configuration errors
---
**Last Updated**: 2026-01-03