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>
99 lines
3.0 KiB
Markdown
99 lines
3.0 KiB
Markdown
# NPMplus Manual Update Required
|
|
|
|
**Last Updated:** 2026-01-31
|
|
**Document Version:** 1.0
|
|
**Status:** Active Documentation
|
|
|
|
---
|
|
|
|
**Date**: 2026-01-18
|
|
**Status**: ⚠️ Configuration script unable to update existing proxy hosts
|
|
**Solution**: Manual update via web UI or API
|
|
|
|
---
|
|
|
|
## Current Situation
|
|
|
|
The configuration script `configure-npmplus-domains.js` has been updated with correct VMIDs and IP addresses, but it cannot automatically update existing proxy hosts (it's designed for new setups). The domains already exist in NPMplus, so they need to be **manually updated** with the correct settings.
|
|
|
|
---
|
|
|
|
## Correct Configuration Reference
|
|
|
|
See `docs/04-configuration/NPMPLUS_CORRECT_CONFIGURATION.md` for complete reference.
|
|
|
|
### Quick Reference
|
|
|
|
| Domain | Target IP | Port | WebSocket | VMID |
|
|
|--------|-----------|------|-----------|------|
|
|
| `explorer.d-bis.org` | 192.168.11.140 | 4000 | ❌ No | 5000 |
|
|
| `rpc-http-pub.d-bis.org` | 192.168.11.221 | 8545 | ✅ Yes | 2201 |
|
|
| `rpc-ws-pub.d-bis.org` | 192.168.11.221 | 8546 | ✅ Yes | 2201 |
|
|
| `rpc-http-prv.d-bis.org` | 192.168.11.211 | 8545 | ✅ Yes | 2101 |
|
|
| `rpc-ws-prv.d-bis.org` | 192.168.11.211 | 8546 | ✅ Yes | 2101 |
|
|
| `rpc.public-0138.defi-oracle.io` | 192.168.11.240 | 443 | ✅ Yes | 2400 |
|
|
| `dbis-admin.d-bis.org` | 192.168.11.130 | 80 | ❌ No | 10130 |
|
|
| `dbis-api.d-bis.org` | 192.168.11.155 | 3000 | ❌ No | 10150 |
|
|
| `dbis-api-2.d-bis.org` | 192.168.11.156 | 3000 | ❌ No | 10151 |
|
|
| `secure.d-bis.org` | 192.168.11.130 | 80 | ❌ No | 10130 |
|
|
| `mim4u.org` | 192.168.11.36 | 80 | ❌ No | 7811 |
|
|
| `secure.mim4u.org` | 192.168.11.36 | 80 | ❌ No | 7811 |
|
|
| `training.mim4u.org` | 192.168.11.36 | 80 | ❌ No | 7811 |
|
|
|
|
---
|
|
|
|
## Manual Update Steps (Web UI)
|
|
|
|
1. **Access NPMplus**:
|
|
- URL: `https://192.168.11.166:81`
|
|
- Email: `nsatoshi2007@hotmail.com`
|
|
- Password: (from `.env` file)
|
|
|
|
2. **For each domain**:
|
|
- Go to **Proxy Hosts** → Find the domain
|
|
- Click **Edit** (pencil icon)
|
|
- Update **Forward Hostname** and **Forward Port** to match the table above
|
|
- Enable/disable **WebSocket Support** as indicated
|
|
- Click **Save**
|
|
|
|
---
|
|
|
|
## Domains to Delete
|
|
|
|
The following Sankofa domains should be **deleted** (services not deployed):
|
|
- `sankofa.nexus`
|
|
- `phoenix.sankofa.nexus`
|
|
- `the-order.sankofa.nexus`
|
|
- `www.sankofa.nexus` (redirect)
|
|
- `www.phoenix.sankofa.nexus` (redirect)
|
|
|
|
---
|
|
|
|
## API-Based Update (Alternative)
|
|
|
|
An API-based update script can be created to programmatically update existing proxy hosts. This would require:
|
|
1. Authenticate to NPMplus API
|
|
2. List all proxy hosts
|
|
3. For each domain, get the host ID
|
|
4. Update the proxy host configuration via PUT request
|
|
|
|
---
|
|
|
|
## Verification
|
|
|
|
After updates, verify each domain:
|
|
|
|
```bash
|
|
# Test RPC endpoints
|
|
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}'
|
|
|
|
# Test explorer
|
|
curl -I https://explorer.d-bis.org/api/v2/stats
|
|
```
|
|
|
|
---
|
|
|
|
**Last Updated**: 2026-01-18
|