# DeFi Oracle Meta Mainnet Connectivity Issue

**Date**: 2026-01-09  
**ChainID**: 138  
**Issue**: Unable to connect to DeFi Oracle Meta Mainnet

---

## Problem Summary

The DeFi Oracle Meta Mainnet (ChainID 138) is not accessible. RPC endpoints are not responding.

---

## RPC Endpoints Tested

### Primary RPC Nodes
- **192.168.11.250:8545** (VMID 2500) - ❌ Not responding
- **192.168.11.251:8545** (VMID 2501) - ❌ Not responding  
- **192.168.11.252:8545** (VMID 2502) - ❌ Not responding

### RPC Translator
- **192.168.11.240:9545** (VMID 2400) - ⏳ Testing...

---

## Expected RPC Endpoints

Based on configuration files, the following RPC endpoints should be available:

1. **Internal Network**:
   - `http://192.168.11.250:8545` (Core RPC)
   - `http://192.168.11.251:8545` (Permissioned RPC)
   - `http://192.168.11.252:8545` (Public RPC)

2. **Public Endpoints** (via Cloudflare Tunnel):
   - `https://rpc-core.d-bis.org`
   - `https://rpc-http-pub.d-bis.org`
   - `https://rpc-http-prv.d-bis.org`
   - `https://rpc.public-0138.defi-oracle.io`

3. **RPC Translator**:
   - `http://192.168.11.240:9545` (ThirdWeb compatible)

---

## Diagnostic Steps

### 1. Check RPC Node Status
```bash
# Check container status
ssh root@192.168.11.10 "pvesh get /nodes/\$(hostname)/lxc/2500/status/current"

# Check Besu service
ssh root@192.168.11.10 "pct exec 2500 -- systemctl status besu-rpc"

# Check if RPC port is listening
ssh root@192.168.11.10 "pct exec 2500 -- netstat -tuln | grep 8545"
```

### 2. Test Local RPC Connection
```bash
# Test from within the container
ssh root@192.168.11.10 "pct exec 2500 -- curl -X POST http://127.0.0.1:8545 \
  -H 'Content-Type: application/json' \
  -d '{\"jsonrpc\":\"2.0\",\"method\":\"eth_chainId\",\"params\":[],\"id\":1}'"
```

### 3. Check Network Connectivity
```bash
# Test network connectivity
ping 192.168.11.250
nc -zv 192.168.11.250 8545
```

### 4. Check Firewall Rules
```bash
# Check if firewall is blocking connections
iptables -L -n | grep 8545
```

---

## Possible Causes

1. **RPC Nodes Not Running**
   - Containers may be stopped
   - Besu services may have crashed
   - Services may not be started

2. **Network Issues**
   - Firewall blocking connections
   - Network routing problems
   - Interface configuration issues

3. **Service Configuration Issues**
   - RPC API not enabled
   - Wrong port configuration
   - Service binding to wrong interface

4. **Resource Issues**
   - Out of memory
   - Disk space full
   - CPU overload

---

## Next Steps

1. ✅ Check RPC node container status
2. ✅ Check Besu service status
3. ✅ Verify RPC port is listening
4. ⏳ Check service logs for errors
5. ⏳ Verify network connectivity
6. ⏳ Check firewall rules
7. ⏳ Restart services if needed

---

## References

- RPC Node Configuration: `docs/05-network/RPC_NODE_TYPES_ARCHITECTURE.md`
- VMID Allocation: `reports/VMID_IP_ADDRESS_LIST.md`
- Network Configuration: `docs/04-configuration/`