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>
152 lines
4.5 KiB
Markdown
152 lines
4.5 KiB
Markdown
# NPMplus Migration - Complete Status
|
|
|
|
**Last Updated:** 2026-01-31
|
|
**Document Version:** 1.0
|
|
**Status:** Active Documentation
|
|
|
|
---
|
|
|
|
**Date**: 2026-01-16
|
|
**Status**: ✅ Migration Complete - SSL Certificates Pending
|
|
|
|
---
|
|
|
|
## ✅ Completed
|
|
|
|
### 1. NPMplus Installation ✅
|
|
- **Container ID**: 10233
|
|
- **Container IP**: 192.168.0.166
|
|
- **Status**: Running and healthy
|
|
- **Access URL**: `https://192.168.0.166:81`
|
|
- **Admin Email**: `nsatoshi2007@hotmail.com`
|
|
- **Admin Password**: `ce8219e321e1cd97bd590fb792d3caeb7e2e3b94ca7e20124acaf253f911ff72`
|
|
|
|
### 2. All 19 Proxy Hosts Configured ✅
|
|
All domains have been successfully configured in NPMplus:
|
|
|
|
#### sankofa.nexus (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 (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 (4 domains)
|
|
- ✅ mim4u.org → http://192.168.11.36:80
|
|
- ✅ www.mim4u.org → http://192.168.11.36:80
|
|
- ✅ secure.mim4u.org → http://192.168.11.36:80
|
|
- ✅ training.mim4u.org → http://192.168.11.36:80
|
|
|
|
#### defi-oracle.io (1 domain)
|
|
- ✅ rpc.public-0138.defi-oracle.io → https://192.168.11.252:443 (WebSocket: ✅)
|
|
|
|
### 3. Backup Created ✅
|
|
- Location: `/tmp/npm-migration-20260116_110359/`
|
|
- Database and configurations backed up
|
|
|
|
---
|
|
|
|
## ⚠️ Pending: SSL Certificates
|
|
|
|
SSL certificate requests are failing with "Internal Error". This is likely because:
|
|
|
|
1. **DNS Not Updated**: Domains need to point to the new NPMplus IP (192.168.0.166)
|
|
2. **Port Forwarding Not Updated**: UDM Pro needs to forward to new container IP
|
|
3. **Let's Encrypt Validation**: Certificates require domains to be accessible from internet
|
|
|
|
### Next Steps for SSL:
|
|
|
|
1. **Update UDM Pro Port Forwarding**:
|
|
- HTTP (Port 80): `76.53.10.36:80` → `192.168.0.166:80`
|
|
- HTTPS (Port 443): `76.53.10.36:443` → `192.168.0.166:443`
|
|
|
|
2. **Verify DNS Records**: Ensure all domains point to `76.53.10.36`
|
|
|
|
3. **Request SSL Certificates**: Once DNS and port forwarding are updated, certificates can be requested via:
|
|
- Web UI: `https://192.168.0.166:81` → SSL Certificates → Request
|
|
- Or wait for automatic renewal attempts
|
|
|
|
---
|
|
|
|
## 📋 Migration Summary
|
|
|
|
| Item | Status |
|
|
|------|--------|
|
|
| NPMplus Installation | ✅ Complete |
|
|
| Container Running | ✅ Healthy |
|
|
| Admin Access | ✅ Working |
|
|
| Proxy Hosts Created | ✅ 19/19 |
|
|
| SSL Certificates | ⚠️ Pending DNS/Network Update |
|
|
| Network Configuration | ⚠️ Needs UDM Pro Update |
|
|
|
|
---
|
|
|
|
## 🔧 API Format Discovered
|
|
|
|
NPMplus uses different API format than standard NPM:
|
|
|
|
**Proxy Host Creation:**
|
|
```json
|
|
{
|
|
"domain_names": ["domain.com"],
|
|
"forward_scheme": "http",
|
|
"forward_host": "192.168.11.140",
|
|
"forward_port": 80,
|
|
"allow_websocket_upgrade": true // optional
|
|
}
|
|
```
|
|
|
|
**SSL Certificate Request:**
|
|
```json
|
|
{
|
|
"domain_names": ["domain.com"],
|
|
"provider": "letsencrypt"
|
|
}
|
|
```
|
|
|
|
---
|
|
|
|
## 🎯 Next Actions
|
|
|
|
1. ✅ **Update UDM Pro Port Forwarding** (Manual)
|
|
- Point to new container IP: `192.168.0.166`
|
|
|
|
2. ✅ **Verify DNS Records** (Manual)
|
|
- Ensure all domains point to `76.53.10.36`
|
|
|
|
3. ✅ **Request SSL Certificates** (After network update)
|
|
- Via web UI or API once domains are accessible
|
|
|
|
4. ✅ **Test All Domains** (After SSL)
|
|
- Verify HTTPS works for all domains
|
|
- Test WebSocket connections for RPC domains
|
|
|
|
5. ✅ **Monitor for 24-48 hours**
|
|
- Ensure certificates renew properly
|
|
- Verify all services are accessible
|
|
|
|
---
|
|
|
|
## 📝 Access Information
|
|
|
|
- **NPMplus URL**: `https://192.168.0.166:81`
|
|
- **Admin Email**: `nsatoshi2007@hotmail.com`
|
|
- **Admin Password**: `ce8219e321e1cd97bd590fb792d3caeb7e2e3b94ca7e20124acaf253f911ff72`
|
|
- **Container ID**: 10233
|
|
- **Container IP**: 192.168.0.166
|
|
|
|
---
|
|
|
|
**Migration Status**: ✅ **Core Migration Complete** - All proxy hosts configured. SSL certificates pending network/DNS updates.
|