178 lines
4.1 KiB
Markdown
178 lines
4.1 KiB
Markdown
|
|
# NPMplus Migration Status
|
||
|
|
|
||
|
|
**Last Updated:** 2026-01-31
|
||
|
|
**Document Version:** 1.0
|
||
|
|
**Status:** Active Documentation
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Date**: 2026-01-16
|
||
|
|
**Status**: Scripts Ready - Manual Installation Required
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## ✅ Completed
|
||
|
|
|
||
|
|
1. **Backup Scripts Created**
|
||
|
|
- ✅ Current NPM backup functionality
|
||
|
|
- ✅ Database export capability
|
||
|
|
- ✅ Configuration export scripts
|
||
|
|
|
||
|
|
2. **Migration Scripts Created**
|
||
|
|
- ✅ `migrate-to-npmplus.sh` - Full automated migration
|
||
|
|
- ✅ `migrate-configs-to-npmplus.sh` - Configuration migration only
|
||
|
|
- ✅ `complete-migration.sh` - Complete orchestration script
|
||
|
|
- ✅ `post-install-migration.sh` - Post-installation automation
|
||
|
|
|
||
|
|
3. **Documentation Created**
|
||
|
|
- ✅ `NPMPLUS_MIGRATION_GUIDE.md` - Complete migration guide
|
||
|
|
- ✅ `NPMPLUS_QUICK_START.md` - Quick start guide
|
||
|
|
- ✅ All 19 domains documented with correct IPs
|
||
|
|
|
||
|
|
4. **Backup Completed**
|
||
|
|
- ✅ Current NPM database backed up
|
||
|
|
- ✅ Backup location: `/tmp/npm-migration-YYYYMMDD_HHMMSS/`
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## ⚠️ Manual Steps Required
|
||
|
|
|
||
|
|
### Step 1: Install NPMplus
|
||
|
|
|
||
|
|
Due to network/DNS issues preventing automated installation, please install NPMplus manually:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
ssh root@192.168.11.11
|
||
|
|
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/npmplus.sh)"
|
||
|
|
```
|
||
|
|
|
||
|
|
**When prompted:**
|
||
|
|
- **Timezone**: `America/New_York`
|
||
|
|
- **ACME Email**: `nsatoshi2007@hotmail.com`
|
||
|
|
|
||
|
|
**After installation:**
|
||
|
|
- Note the container ID (VMID)
|
||
|
|
- Note the container IP address
|
||
|
|
- Get admin password: `pct exec <CTID> -- cat /opt/.npm_pwd`
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### Step 2: Run Post-Installation Migration
|
||
|
|
|
||
|
|
After NPMplus is installed, run:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
bash scripts/nginx-proxy-manager/post-install-migration.sh \
|
||
|
|
192.168.11.11 \
|
||
|
|
<CONTAINER_ID> \
|
||
|
|
<CONTAINER_IP>
|
||
|
|
```
|
||
|
|
|
||
|
|
Or use the complete migration script:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
bash scripts/nginx-proxy-manager/complete-migration.sh
|
||
|
|
```
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### Step 3: Update UDM Pro Port Forwarding
|
||
|
|
|
||
|
|
1. Log into UDM Pro
|
||
|
|
2. **Settings** → **Networks** → **Port Forwarding**
|
||
|
|
3. Update both rules:
|
||
|
|
- **HTTP (Port 80)**: `76.53.10.36:80` → `<new-npmplus-ip>:80`
|
||
|
|
- **HTTPS (Port 443)**: `76.53.10.36:443` → `<new-npmplus-ip>:443`
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### Step 4: Verify Migration
|
||
|
|
|
||
|
|
```bash
|
||
|
|
# Test SSL certificates
|
||
|
|
bash scripts/check-east-west-ssl-status.sh
|
||
|
|
|
||
|
|
# Test admin UI
|
||
|
|
curl -k https://<npmplus-ip>:81
|
||
|
|
```
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## 📋 What Gets Migrated
|
||
|
|
|
||
|
|
All 19 domains will be automatically configured:
|
||
|
|
|
||
|
|
### sankofa.nexus (5 domains)
|
||
|
|
- sankofa.nexus
|
||
|
|
- www.sankofa.nexus
|
||
|
|
- phoenix.sankofa.nexus
|
||
|
|
- www.phoenix.sankofa.nexus
|
||
|
|
- the-order.sankofa.nexus
|
||
|
|
|
||
|
|
### d-bis.org (9 domains)
|
||
|
|
- explorer.d-bis.org
|
||
|
|
- rpc-http-pub.d-bis.org
|
||
|
|
- rpc-ws-pub.d-bis.org
|
||
|
|
- rpc-http-prv.d-bis.org
|
||
|
|
- rpc-ws-prv.d-bis.org
|
||
|
|
- dbis-admin.d-bis.org
|
||
|
|
- dbis-api.d-bis.org
|
||
|
|
- dbis-api-2.d-bis.org
|
||
|
|
- secure.d-bis.org
|
||
|
|
|
||
|
|
### mim4u.org (4 domains)
|
||
|
|
- mim4u.org
|
||
|
|
- www.mim4u.org
|
||
|
|
- secure.mim4u.org
|
||
|
|
- training.mim4u.org
|
||
|
|
|
||
|
|
### defi-oracle.io (1 domain)
|
||
|
|
- rpc.public-0138.defi-oracle.io
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## 🔧 Troubleshooting
|
||
|
|
|
||
|
|
### Installation Fails
|
||
|
|
|
||
|
|
- Check DNS resolution on Proxmox host
|
||
|
|
- Verify internet connectivity
|
||
|
|
- Check Proxmox storage availability
|
||
|
|
|
||
|
|
### Migration Script Fails
|
||
|
|
|
||
|
|
- Verify NPMplus is running: `pct exec <CTID> -- docker ps`
|
||
|
|
- Check admin password: `pct exec <CTID> -- cat /opt/.npm_pwd`
|
||
|
|
- Verify container IP is correct
|
||
|
|
- Check API access: `curl -k https://<ip>:81/api`
|
||
|
|
|
||
|
|
### SSL Certificates Not Issuing
|
||
|
|
|
||
|
|
- Verify DNS records point to `76.53.10.36`
|
||
|
|
- Wait 1-2 minutes for Let's Encrypt processing
|
||
|
|
- Check NPMplus logs: `docker logs npmplus`
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## 📁 Scripts Available
|
||
|
|
|
||
|
|
1. **`complete-migration.sh`** - Full orchestration (recommended)
|
||
|
|
2. **`post-install-migration.sh`** - After NPMplus is installed
|
||
|
|
3. **`migrate-configs-to-npmplus.sh`** - Configuration migration only
|
||
|
|
4. **`migrate-to-npmplus.sh`** - Full automated (requires NPMplus installed)
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## 🎯 Next Actions
|
||
|
|
|
||
|
|
1. ✅ Install NPMplus manually (see Step 1 above)
|
||
|
|
2. ✅ Run post-installation migration script
|
||
|
|
3. ✅ Update UDM Pro port forwarding
|
||
|
|
4. ✅ Verify all domains and SSL certificates
|
||
|
|
5. ✅ Monitor for 24-48 hours
|
||
|
|
6. ✅ (Optional) Stop old NPM container after verification
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**All scripts and documentation are ready. Proceed with manual NPMplus installation, then run the migration scripts.**
|