proxmox/docs/04-configuration/NPMPLUS_MIGRATION_COMPLETE_STATUS.md

NPMplus Migration - Complete Status

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

---

Date: 2026-01-16
Status: NPMplus Installed - Configuration Migration In Progress

---

✅ Completed Steps

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: admin@example.org
   • Admin Password: ce8219e321e1cd97bd590fb792d3caeb7e2e3b94ca7e20124acaf253f911ff72

2. Backup Created ✅

   • Location: /tmp/npm-migration-20260116_110359/
   • Database and configurations backed up

3. Dependencies Installed ✅

   • Docker installed and running
   • Docker Compose plugin installed
   • jq installed for JSON parsing
   • NPMplus container healthy

---

⚠️ Current Issue

API Format Mismatch: NPMplus uses a different API format than standard NPM.

The error "data must NOT have additional properties" indicates that NPMplus API:

• Uses forward_host instead of forward_hostname ✅ (fixed)
• May not accept all the fields we're sending
• Requires different field structure

---

🔧 Solution Options

Option 1: Manual Configuration via Web UI (Recommended for Now)

1. Access NPMplus: https://192.168.0.166:81
2. Login with:
   • Email: admin@example.org
   • Password: ce8219e321e1cd97bd590fb792d3caeb7e2e3b94ca7e20124acaf253f911ff72
3. Configure each domain manually (19 domains total)

Option 2: Fix API Script

Need to determine the exact API schema for NPMplus. The API format differs from standard NPM.

Option 3: Use Browser Automation

Use Playwright script to automate web UI configuration (similar to existing configure-ssl-all-domains.js)

---

📋 All 19 Domains to Configure

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: ✅)

---

🔍 Next Steps

1. Determine NPMplus API Schema

   • Check NPMplus GitHub repository for API documentation
   • Or inspect API responses to understand required fields

2. Update Migration Script

   • Fix API payload format
   • Test with one domain first
   • Then migrate all 19 domains

3. Alternative: Browser Automation

   • Adapt existing Playwright script for NPMplus
   • Automate web UI configuration

4. Update Network Configuration

   • Update UDM Pro port forwarding to 192.168.0.166
   • Test all domains after configuration

---

📝 Notes

• NPMplus is successfully installed and running
• Authentication works correctly
• API format needs adjustment for NPMplus-specific schema
• All infrastructure is ready for configuration

---

Current Status: Ready for domain configuration once API format is resolved.