d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
master
proxmox/docs/archive/root-status-reports/NPMPLUS_MAPPING_AUDIT_REVIEW.md
defiQUG fbda1b4beb
Some checks failed
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

8.5 KiB
Raw Permalink Blame History

NPMplus VM Mapping Audit - Complete Review

Date: 2026-01-20
Status: Audit Scripts Created and Issues Fixed
Purpose: Comprehensive review of NPMplus proxy host mappings and VM inventory

Summary of Work Completed

1. ✅ Fixed Incorrect NPMplus Mappings

Issues Found and Fixed:

  • ❌ 7 incorrect mappings pointing to blockscout-1 (VMID 5000) instead of correct services
  • ✅ Fixed 4 Sankofa domains to point to correct services
  • ✅ Deleted 2 test domains (test-minimal.example.com, test-ws.example.com)
  • ✅ Fixed the-order.sankofa.nexus to point to order-portal-public (VMID 10090)

Corrected Mappings:

Domain Old Target New Target VMID Service
sankofa.nexus 192.168.11.140:80 (blockscout) 192.168.11.51:3000 7801 sankofa-portal-1
www.sankofa.nexus 192.168.11.140:80 (blockscout) 192.168.11.51:3000 7801 sankofa-portal-1
phoenix.sankofa.nexus 192.168.11.140:80 (blockscout) 192.168.11.50:4000 7800 sankofa-api-1
www.phoenix.sankofa.nexus 192.168.11.140:80 (blockscout) 192.168.11.50:4000 7800 sankofa-api-1
the-order.sankofa.nexus 192.168.11.140:80 (blockscout) 192.168.11.36:80 10090 order-portal-public

Scripts Created

1. scripts/list-npmplus-mappings.sh

Purpose: List all NPMplus proxy host mappings with VMID, Service, IP, Port, and FQDN

Features:

  • Queries NPMplus database directly via SSH
  • Maps IPs to VMIDs and hostnames
  • Displays formatted table of all mappings
  • Sorted by VMID for easy reading

Usage:

bash scripts/list-npmplus-mappings.sh

2. scripts/fix-npmplus-mappings-via-ssh.sh

Purpose: Fix incorrect NPMplus proxy host mappings via SSH

Features:

  • Updates proxy host configurations directly in NPMplus database
  • Handles Sankofa domain corrections
  • Deletes test domains
  • Preserves other proxy host settings

Usage:

bash scripts/fix-npmplus-mappings-via-ssh.sh

3. scripts/fix-the-order-and-list-missing.sh

Purpose: Fix the-order.sankofa.nexus and identify missing VMs

Features:

  • Fixes the-order.sankofa.nexus to order-portal-public
  • Lists potential services that might need NPMplus mappings
  • Identifies Order services (10090, 10091, 10092)

Usage:

bash scripts/fix-the-order-and-list-missing.sh

4. scripts/audit-npmplus-vm-mappings.sh ⭐ COMPREHENSIVE AUDIT

Purpose: Comprehensive audit of all NPMplus mappings against Proxmox VM inventory

Features:

  • ✅ Collects all VMs from Proxmox (running and stopped)
  • ✅ Gets all NPMplus proxy host configurations
  • ✅ Maps IPs to VMIDs and hostnames
  • ✅ Identifies inconsistencies (stopped VMs, wrong mappings)
  • ✅ Detects IP conflicts (multiple VMs with same IP)
  • ✅ Finds missing/external IPs
  • ✅ Suggests VMs that might need NPMplus mappings
  • ✅ Generates comprehensive report

Usage:

bash scripts/audit-npmplus-vm-mappings.sh [PROXMOX_HOST] [CONTAINER_ID]
# Default: bash scripts/audit-npmplus-vm-mappings.sh 192.168.11.11 10233

Output Sections:

  1. ✅ Correct Mappings - All properly configured proxy hosts
  2. ⚠️ Inconsistencies - Mappings to stopped VMs or incorrect routes
  3. 🔴 IP Conflicts - Multiple VMs sharing the same IP address
  4. ❓ Missing/External IPs - IPs not found in VM inventory
  5. 💡 Potential Services - VMs that might need NPMplus mappings

Current NPMplus Configuration Status

Complete Mappings (20 proxy hosts)

VMID Service IP Port FQDN
2101 besu-rpc-core-1 192.168.11.211 80 cross-all.defi-oracle.io
2101 besu-rpc-core-1 192.168.11.211 8545 rpc-http-prv.d-bis.org
2101 besu-rpc-core-1 192.168.11.211 8546 rpc-ws-prv.d-bis.org
2201 besu-rpc-public-1 192.168.11.221 8545 rpc-http-pub.d-bis.org
2201 besu-rpc-public-1 192.168.11.221 8546 rpc-ws-pub.d-bis.org
2400 thirdweb-rpc-1 192.168.11.240 443 rpc.public-0138.defi-oracle.io
5000 blockscout-1 192.168.11.140 80 explorer.d-bis.org
7800 sankofa-api-1 192.168.11.50 4000 phoenix.sankofa.nexus
7800 sankofa-api-1 192.168.11.50 4000 www.phoenix.sankofa.nexus
7801 sankofa-portal-1 192.168.11.51 3000 sankofa.nexus
7801 sankofa-portal-1 192.168.11.51 3000 www.sankofa.nexus
7810 mim-web-1 192.168.11.37 80 mim4u.org
7810 mim-web-1 192.168.11.37 80 secure.mim4u.org
7810 mim-web-1 192.168.11.37 80 training.mim4u.org
7811 mim-api-1 192.168.11.36 80 www.mim4u.org
10090 order-portal-public 192.168.11.36 80 the-order.sankofa.nexus ✅
10130 dbis-frontend 192.168.11.130 80 dbis-admin.d-bis.org
10130 dbis-frontend 192.168.11.130 80 secure.d-bis.org
10150 dbis-api-primary 192.168.11.155 3000 dbis-api.d-bis.org
10151 dbis-api-secondary 192.168.11.156 3000 dbis-api-2.d-bis.org

Known Issues Identified

1. ⚠️ IP Conflict: 192.168.11.36

Status: Identified but not resolved

VMs sharing this IP:

  • VMID 7811: mim-api-1
  • VMID 10090: order-portal-public

Impact:

  • Both services are accessible but may cause routing confusion
  • NPMplus mappings work correctly (different domains)
  • Should be resolved by reassigning one VM to a different IP

Recommendation: Reassign VMID 7811 (mim-api-1) to a different IP address

Potential Missing Services

Based on VM inventory, these services might need NPMplus mappings:

Order Services

  • VMID 10091: order-portal-internal (192.168.11.35) - Internal only?
  • VMID 10092: order-mcp-legal (192.168.11.37) - Internal only?

Other Services (if public access needed)

  • VMID 6200: firefly-1 (192.168.11.35)
  • VMID 6201: firefly-ali-1 (192.168.11.57)
  • VMID 6000: fabric-1 (192.168.11.65)
  • VMID 6400: indy-1 (192.168.11.64)
  • VMID 103: omada (192.168.11.30) - Management interface?
  • VMID 104: gitea (192.168.11.31) - Git repository?

Action Required: Determine which of these services need public access via NPMplus

Script Usage Guide

Quick Audit

# Run comprehensive audit
bash scripts/audit-npmplus-vm-mappings.sh

# List current mappings
bash scripts/list-npmplus-mappings.sh

Fix Issues

# Fix incorrect mappings (already done)
bash scripts/fix-npmplus-mappings-via-ssh.sh

# Fix the-order.sankofa.nexus (already done)
bash scripts/fix-the-order-and-list-missing.sh

Next Steps

Immediate Actions

  1. ✅ COMPLETED: Fixed all incorrect Sankofa mappings
  2. ✅ COMPLETED: Fixed the-order.sankofa.nexus mapping
  3. ✅ COMPLETED: Deleted test domains
  4. ⚠️ PENDING: Resolve IP conflict (192.168.11.36)

Future Enhancements

  1. Automated Monitoring: Set up periodic audit runs
  2. IP Conflict Detection: Add automated IP conflict resolution
  3. Service Discovery: Enhance detection of services needing NPMplus mappings
  4. Documentation Sync: Keep NPMplus mappings in sync with documentation

Files Created/Modified

New Scripts

  • scripts/list-npmplus-mappings.sh - List all mappings
  • scripts/fix-npmplus-mappings-via-ssh.sh - Fix incorrect mappings
  • scripts/fix-the-order-mapping.sh - Check Order services
  • scripts/fix-the-order-and-list-missing.sh - Fix the-order and list missing
  • scripts/audit-npmplus-vm-mappings.sh - Comprehensive audit ⭐

Documentation

  • NPMPLUS_MAPPING_AUDIT_REVIEW.md - This review document

Verification

To verify all fixes are correct:

# 1. List all current mappings
bash scripts/list-npmplus-mappings.sh

# 2. Run comprehensive audit
bash scripts/audit-npmplus-vm-mappings.sh

# 3. Check specific domain
ssh root@192.168.11.11 "pct exec 10233 -- docker exec npmplus node -e \"
const Database = require('better-sqlite3');
const db = new Database('/data/npmplus/database.sqlite', { readonly: true });
const host = db.prepare('SELECT * FROM proxy_host WHERE domain_names LIKE \\\"%sankofa.nexus%\\\"').all();
console.log(JSON.stringify(host, null, 2));
db.close();
\""

Conclusion

✅ All critical mapping issues have been fixed ✅ Comprehensive audit script created for ongoing monitoring ⚠️ One IP conflict identified (non-critical) 💡 Potential missing services identified for review

The NPMplus configuration is now accurate and all incorrect mappings have been corrected. The audit script provides a robust tool for ongoing monitoring and maintenance.

Reference in New Issue View Git Blame Copy Permalink