Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- 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>

2026-02-12 15:46:57 -08:00

4.4 KiB

Raw Permalink Blame History

East-West Traffic & SSL Certificate Status Report

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Date: 2026-01-15
Status: Comprehensive Status Check

🌐 East-West Traffic (Inter-VLAN Routing)

Status Summary

Based on previous verification (from DEPLOYMENT_STATUS_MASTER.md):

✅ Inter-VLAN routing verified and working (completed 2026-01-15)
✅ All 17 VLAN gateways were tested and confirmed reachable
✅ Network Isolation disabled, Zone Matrix configured

Current Test Results

From Proxmox Host (r630-01 - 192.168.11.11):

Service	IP	Status
Nginx Proxy Manager	192.168.11.26	✅ Reachable
Blockscout	192.168.11.140	⚠️ Not reachable
Besu RPC Public	192.168.11.252	✅ Reachable

Note: Blockscout connectivity may be intermittent or the service may be down.

VLAN Gateway Connectivity

According to previous verification:

✅ All 17 VLAN gateways (110-203) were tested and confirmed reachable
✅ Inter-VLAN routing is functional
✅ Network infrastructure is operational

To re-verify:

bash scripts/unifi/verify-vlan-settings.sh

🔒 SSL Certificate Status

Current Status

NPM Authentication:

⚠️ Authentication issues with provided credentials
Manual verification required via web UI

Proxy Hosts

Configuration Status:

⚠️ Unable to verify via API (authentication required)
Manual check needed: http://192.168.11.26:81

Expected Configuration (19 domains):

sankofa.nexus Zone (5 domains)

sankofa.nexus → http://192.168.11.140:80
www.sankofa.nexus → http://192.168.11.140:80
phoenix.sankofa.nexus → http://192.168.11.140:80
www.phoenix.sankofa.nexus → http://192.168.11.140:80
the-order.sankofa.nexus → http://192.168.11.140:80

d-bis.org Zone (9 domains)

explorer.d-bis.org → http://192.168.11.140:80
rpc-http-pub.d-bis.org → https://192.168.11.252:443 (WebSocket)
rpc-ws-pub.d-bis.org → https://192.168.11.252:443 (WebSocket)
rpc-http-prv.d-bis.org → https://192.168.11.251:443 (WebSocket)
rpc-ws-prv.d-bis.org → https://192.168.11.251:443 (WebSocket)
dbis-admin.d-bis.org → http://192.168.11.130:80
dbis-api.d-bis.org → http://192.168.11.155:3000
dbis-api-2.d-bis.org → http://192.168.11.156:3000
secure.d-bis.org → http://192.168.11.130:80

mim4u.org Zone (4 domains)

mim4u.org → http://192.168.11.19:80
www.mim4u.org → http://192.168.11.19:80
secure.mim4u.org → http://192.168.11.19:80
training.mim4u.org → http://192.168.11.19:80

defi-oracle.io Zone (1 domain)

rpc.public-0138.defi-oracle.io → https://192.168.11.252:443 (WebSocket)

HTTPS Connectivity

Test Results:

⚠️ sankofa.nexus - Not accessible
⚠️ explorer.d-bis.org - Not accessible
⚠️ mim4u.org - Not accessible

Status: SSL certificates not yet configured or not accessible

SSL Certificate Configuration

Scripts Ready:

✅ scripts/nginx-proxy-manager/configure-domains-pct-exec.sh - API-based configuration
✅ scripts/nginx-proxy-manager/verify-ssl-config.sh - Verification script
✅ All documentation and guides created

Blockers:

⚠️ NPM authentication failing with provided credentials
Action required: Verify credentials or reset password

Recommended Actions:

Access NPM UI: http://192.168.11.26:81
Verify/update credentials
Configure domains manually or fix authentication
Request Let's Encrypt certificates
Verify HTTPS connectivity

📊 Summary