fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
145 lines
3.9 KiB
Markdown
145 lines
3.9 KiB
Markdown
# DeFi Oracle Meta Mainnet Connectivity - Complete Diagnosis
|
|
|
|
**Date**: 2026-01-09
|
|
**ChainID**: 138 (0x8a)
|
|
**Status**: ⚠️ **Internal Endpoints Working, Public Endpoints Down**
|
|
|
|
---
|
|
|
|
## Executive Summary
|
|
|
|
**Internal RPC endpoints are fully operational**, but **public endpoints via Cloudflare tunnel are not accessible**. This means:
|
|
|
|
- ✅ **Internal network access**: Working perfectly
|
|
- ❌ **External/public access**: Not working (Cloudflare tunnel issue)
|
|
|
|
---
|
|
|
|
## ✅ Working Endpoints (Internal Network)
|
|
|
|
All internal RPC endpoints are responding correctly:
|
|
|
|
1. **RPC Translator**: `http://192.168.11.240:9545` ✅
|
|
- ChainID: `0x8a` (138)
|
|
- Status: Fully operational
|
|
|
|
2. **Core RPC**: `http://192.168.11.250:8545` ✅
|
|
- ChainID: `0x8a` (138)
|
|
- Status: Fully operational
|
|
|
|
3. **Permissioned RPC**: `http://192.168.11.251:8545` ✅
|
|
- ChainID: `0x8a` (138)
|
|
- Status: Fully operational
|
|
|
|
4. **Public RPC**: `http://192.168.11.252:8545` ✅
|
|
- ChainID: `0x8a` (138)
|
|
- Status: Fully operational
|
|
|
|
---
|
|
|
|
## ❌ Non-Working Endpoints (Public/External)
|
|
|
|
Public endpoints via Cloudflare tunnel are returning error 1033:
|
|
|
|
1. **rpc-http-pub.d-bis.org**: ❌ Cloudflare error 1033
|
|
2. **rpc-core.d-bis.org**: ❌ Connection failed
|
|
3. **rpc.d-bis.org**: ❌ Connection failed
|
|
|
|
**Root Cause**: Cloudflare tunnel (VMID 102) is not running or misconfigured.
|
|
|
|
---
|
|
|
|
## Issue Analysis
|
|
|
|
### Cloudflare Tunnel Status
|
|
|
|
- **VMID 102**: Status unknown (needs verification)
|
|
- **cloudflared binary**: Not found in container
|
|
- **cloudflared service**: Not running or not configured
|
|
|
|
### Expected Routing
|
|
|
|
```
|
|
Internet → Cloudflare → cloudflared (VMID 102) → Central Nginx (VMID 105) → RPC Node (VMID 2502)
|
|
```
|
|
|
|
**Current Status**: Tunnel is not operational, breaking the chain.
|
|
|
|
---
|
|
|
|
## Solutions
|
|
|
|
### Option 1: Use Internal Endpoints (Immediate Solution)
|
|
|
|
If you're on the internal network (192.168.11.0/24), use these endpoints:
|
|
|
|
**For MetaMask/dApps**:
|
|
- `http://192.168.11.240:9545` (RPC Translator - ThirdWeb compatible)
|
|
- `http://192.168.11.250:8545` (Core RPC)
|
|
|
|
**For Development**:
|
|
- `http://192.168.11.251:8545` (Permissioned RPC)
|
|
- `http://192.168.11.252:8545` (Public RPC)
|
|
|
|
### Option 2: Fix Cloudflare Tunnel (For External Access)
|
|
|
|
To restore public endpoint access:
|
|
|
|
1. **Install/Configure cloudflared on VMID 102**
|
|
2. **Configure tunnel in Cloudflare dashboard**
|
|
3. **Set up routing to central Nginx (VMID 105)**
|
|
4. **Verify tunnel is running**
|
|
|
|
---
|
|
|
|
## Recommended Action
|
|
|
|
**For immediate use**: Use internal endpoints if you're on the same network.
|
|
|
|
**For public access**: The Cloudflare tunnel needs to be configured and started. This requires:
|
|
- Cloudflare Zero Trust account access
|
|
- Tunnel configuration in Cloudflare dashboard
|
|
- cloudflared service running on VMID 102
|
|
|
|
---
|
|
|
|
## Testing Commands
|
|
|
|
### Test Internal Endpoints
|
|
```bash
|
|
# RPC Translator
|
|
curl -X POST http://192.168.11.240:9545 \
|
|
-H 'Content-Type: application/json' \
|
|
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
|
|
|
|
# Core RPC
|
|
curl -X POST http://192.168.11.250:8545 \
|
|
-H 'Content-Type: application/json' \
|
|
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
|
|
```
|
|
|
|
### Test Public Endpoints
|
|
```bash
|
|
# Should work once tunnel is fixed
|
|
curl -X POST https://rpc-http-pub.d-bis.org \
|
|
-H 'Content-Type: application/json' \
|
|
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
|
|
```
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. ✅ **Internal endpoints verified working** - Use these for now
|
|
2. ⏳ **Fix Cloudflare tunnel** - Install and configure cloudflared on VMID 102
|
|
3. ⏳ **Configure tunnel routing** - Set up hostname routing in Cloudflare dashboard
|
|
4. ⏳ **Test public endpoints** - Verify external access works
|
|
|
|
---
|
|
|
|
## References
|
|
|
|
- Connection Guide: `reports/DEFI_ORACLE_MAINNET_CONNECTION_GUIDE.md`
|
|
- Cloudflare Tunnel Config: `docs/04-configuration/cloudflare/CLOUDFLARE_TUNNEL_CONFIGURATION_GUIDE.md`
|
|
- Network Architecture: `docs/05-network/CLOUDFLARE_TUNNEL_ROUTING_ARCHITECTURE.md`
|