Files
proxmox/docs/04-configuration/NPMPLUS_CORRECT_CONFIGURATION.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
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.6 KiB

NPMplus Correct Configuration Reference

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


Date: 2026-01-18
Status: Verified and Updated
Purpose: Authoritative reference for correct VMID and IP mappings in NPMplus


Complete Domain Configuration

Blockchain Explorer

Domain Target IP Port VMID Service WebSocket
explorer.d-bis.org 192.168.11.140 80 5000 blockscout-1 No

Note: Routes to nginx on port 80 which serves the Blockscout web UI. nginx internally proxies /api/* requests to Blockscout API on port 4000.


RPC Endpoints (d-bis.org)

Public RPC (VMID 2201: besu-rpc-public-1)

Domain Target IP Port Protocol WebSocket
rpc-http-pub.d-bis.org 192.168.11.221 8545 HTTP Yes
rpc-ws-pub.d-bis.org 192.168.11.221 8546 HTTP Yes
rpc.d-bis.org 192.168.11.221 8545 HTTP Yes
rpc2.d-bis.org 192.168.11.221 8545 HTTP Yes
ws.rpc.d-bis.org 192.168.11.221 8546 HTTP Yes
ws.rpc2.d-bis.org 192.168.11.221 8546 HTTP Yes

Private RPC (VMID 2101: besu-rpc-core-1)

Domain Target IP Port Protocol WebSocket
rpc-http-prv.d-bis.org 192.168.11.211 8545 HTTP Yes
rpc-ws-prv.d-bis.org 192.168.11.211 8546 HTTP Yes

ThirdWeb RPC (defi-oracle.io)

Domain Target IP Port Protocol VMID Service WebSocket
rpc.public-0138.defi-oracle.io 192.168.11.240 443 HTTPS 2400 thirdweb-rpc-1 Yes
rpc.defi-oracle.io 192.168.11.221 8545 HTTP 2201 besu-rpc-public-1 Yes
wss.defi-oracle.io 192.168.11.221 8546 HTTP 2201 besu-rpc-public-1 Yes

Note: Uses HTTPS on port 443 (Nginx with RPC Translator).


DBIS Core Services (d-bis.org)

Domain Target IP Port VMID Service WebSocket
dbis-admin.d-bis.org 192.168.11.130 80 10130 dbis-frontend No
dbis-api.d-bis.org 192.168.11.155 3000 10150 dbis-api-primary No
dbis-api-2.d-bis.org 192.168.11.156 3000 10151 dbis-api-secondary No
secure.d-bis.org 192.168.11.130 80 10130 dbis-frontend No

Note: secure.d-bis.org uses path-based routing internally (handled by backend nginx).


MIM4U Services (mim4u.org)

Domain Target IP Port VMID Service WebSocket
mim4u.org 192.168.11.37 80 7810 mim-web-1 No
secure.mim4u.org 192.168.11.37 80 7810 mim-web-1 No
training.mim4u.org 192.168.11.37 80 7810 mim-web-1 No

Redirects

Domain Redirects To
www.mim4u.org mim4u.org

Removed Domains (Not Deployed)

The following domains have been removed from configuration as services are not deployed:

  • sankofa.nexus - ⚠️ Previously incorrectly routed to Blockscout
  • www.sankofa.nexus - ⚠️ Previously incorrectly routed to Blockscout
  • phoenix.sankofa.nexus - ⚠️ Previously incorrectly routed to Blockscout
  • www.phoenix.sankofa.nexus - ⚠️ Previously incorrectly routed to Blockscout
  • the-order.sankofa.nexus - ⚠️ Previously incorrectly routed to Blockscout

Action Required: When Sankofa services are deployed, add these domains back with correct backend IPs.


Configuration Summary

Total Proxy Hosts: 13
Total Redirects: 1
WebSocket Enabled: 5 domains
HTTPS Backend: 1 domain (ThirdWeb RPC)


Verification

All configurations match the authoritative sources:

  • docs/04-configuration/RPC_ENDPOINTS_MASTER.md
  • docs/04-configuration/ALL_VMIDS_ENDPOINTS.md

For ChainID 138 public RPCs, Proxmox VM / NPMplus mapping, and Ledger App-Ethereum access, see PUBLIC_RPC_CHAIN138_LEDGER.md.


Update Script

Configuration is managed by:

  • Script: scripts/nginx-proxy-manager/configure-npmplus-domains.js
  • Last Updated: 2026-01-18

To apply configuration:

cd /home/intlc/projects/proxmox
node scripts/nginx-proxy-manager/configure-npmplus-domains.js

Last Updated: 2026-01-18
Maintained By: Infrastructure Team