Files
proxmox/docs/04-configuration/NPMPLUS_UPDATE_COMPLETE.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

105 lines
2.9 KiB
Markdown

# NPMplus Configuration Update - Complete
**Last Updated:** 2026-01-31
**Document Version:** 1.0
**Status:** Active Documentation
---
**Date**: 2026-01-18
**Status**: ✅ **ALL UPDATES SUCCESSFUL**
---
## Summary
Successfully updated all 13 NPMplus proxy hosts with correct VMIDs and IP addresses via API.
---
## Updated Proxy Hosts
### ✅ Blockchain Explorer
- `explorer.d-bis.org``http://192.168.11.140:4000` (VMID 5000)
- **Changed**: Port from 80 → 4000 (direct Blockscout route)
### ✅ RPC Endpoints
**Public RPC** (VMID 2201):
- `rpc-http-pub.d-bis.org``http://192.168.11.221:8545`
- `rpc-ws-pub.d-bis.org``http://192.168.11.221:8546`
**Private RPC** (VMID 2101):
- `rpc-http-prv.d-bis.org``http://192.168.11.211:8545`
- `rpc-ws-prv.d-bis.org``http://192.168.11.211:8546`
**ThirdWeb RPC** (VMID 2400):
- `rpc.public-0138.defi-oracle.io``https://192.168.11.240:443`
### ✅ DBIS Services
- `dbis-admin.d-bis.org``http://192.168.11.130:80` (VMID 10130) ✅
- `dbis-api.d-bis.org``http://192.168.11.155:3000` (VMID 10150) ✅
- `dbis-api-2.d-bis.org``http://192.168.11.156:3000` (VMID 10151) ✅
- `secure.d-bis.org``http://192.168.11.130:80` (VMID 10130) ✅
### ✅ MIM4U Services
**Updated to use VMID 7810 (mim-web-1)**:
- `mim4u.org``http://192.168.11.37:80` (was 192.168.11.36) ✅
- `secure.mim4u.org``http://192.168.11.37:80`
- `training.mim4u.org``http://192.168.11.37:80`
---
## Changes Made
### 1. Explorer Port Fix
- **Before**: `explorer.d-bis.org``192.168.11.140:80` (via nginx)
- **After**: `explorer.d-bis.org``192.168.11.140:4000` (direct Blockscout)
- **Impact**: Now routes directly to Blockscout API, bypassing nginx
### 2. RPC Endpoint IPs
All RPC endpoints now use correct IPs after VMID migration:
- Public RPC: 192.168.11.221 (VMID 2201)
- Private RPC: 192.168.11.211 (VMID 2101)
- ThirdWeb RPC: 192.168.11.240 (VMID 2400)
### 3. MIM4U Frontend Update
- **Before**: All domains routed to `192.168.11.36` (mim-api-1, VMID 7811)
- **After**: All domains route to `192.168.11.37` (mim-web-1, VMID 7810)
- **Reason**: Frontend web server handles static files and proxies `/api/*` to backend
---
## Script Used
**Script**: `scripts/nginx-proxy-manager/update-npmplus-proxy-hosts-api.sh`
**Fix Applied**:
- Changed from sending full host object to minimal payload
- Only sends: `forward_scheme`, `forward_host`, `forward_port`, `allow_websocket_upgrade`
- NPMplus API rejects additional properties in update requests
---
## Verification
All 13 proxy hosts updated successfully:
-**Updated**: 13
-**Failed**: 0
---
## Next Steps
1. ✅ All NPMplus configurations updated
2. ⏸️ Verify services are accessible via updated domains
3. ⏸️ Test RPC endpoints to confirm correct routing
4. ⏸️ Test MIM4U domains to verify frontend routing
---
**Last Updated**: 2026-01-18
**Script**: `update-npmplus-proxy-hosts-api.sh`