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>
3.7 KiB
3.7 KiB
NPMplus Quick Start Guide
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Quick migration from Nginx Proxy Manager to NPMplus
Step 1: Install NPMplus
On your Proxmox host, run:
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/npmplus.sh)"
During installation:
- Enter timezone:
America/New_York(or your timezone) - Enter ACME email:
nsatoshi2007@hotmail.com - Note the container ID (VMID) that gets created
- Wait 1-2 minutes for NPMplus to start
After installation:
- Access URL:
https://<container-IP>:81 - Default email:
admin@example.org - Get password:
pct exec <CTID> -- cat /opt/.npm_pwd
Step 2: Get Container Information
# Get container ID and IP
ssh root@192.168.11.11 "pct list | grep npmplus"
# Get container IP
ssh root@192.168.11.11 "pct exec <CTID> -- hostname -I | awk '{print \$1}'"
# Get admin password
ssh root@192.168.11.11 "pct exec <CTID> -- cat /opt/.npm_pwd"
Step 3: Migrate Configurations
Run the migration script:
bash scripts/nginx-proxy-manager/migrate-configs-to-npmplus.sh \
192.168.11.11 \
<CONTAINER_ID> \
https://<CONTAINER_IP>:81
Or run interactively:
bash scripts/nginx-proxy-manager/migrate-configs-to-npmplus.sh
This will:
- ✅ Configure all 19 domains
- ✅ Request SSL certificates for all domains
- ✅ Enable HTTPS, HTTP/2, HSTS, and security features
Step 4: Update Network Configuration
Update UDM Pro Port Forwarding
- Log into UDM Pro
- Settings → Networks → Port Forwarding
- Update both rules:
- HTTP (80):
76.53.10.36:80→<new-npmplus-ip>:80 - HTTPS (443):
76.53.10.36:443→<new-npmplus-ip>:443
- HTTP (80):
Step 5: Verify Migration
# Test SSL certificates
bash scripts/check-east-west-ssl-status.sh
# Test admin UI
curl -k https://<npmplus-ip>:81
# Check all domains are accessible
for domain in sankofa.nexus explorer.d-bis.org mim4u.org; do
echo "Testing $domain..."
curl -I https://$domain 2>&1 | head -1
done
Troubleshooting
Cannot Access Admin UI
# Check container status
ssh root@192.168.11.11 "pct status <CTID>"
# Check Docker logs
ssh root@192.168.11.11 "pct exec <CTID> -- docker logs npmplus"
# Check if port 81 is listening
ssh root@192.168.11.11 "pct exec <CTID> -- netstat -tlnp | grep 81"
SSL Certificates Not Issuing
- Verify DNS records point to
76.53.10.36 - Wait 1-2 minutes for Let's Encrypt to process
- Check NPMplus logs:
docker logs npmplus | grep -i cert
Migration Script Fails
- Check authentication: Try logging into web UI manually
- Verify container ID and IP are correct
- Check if jq is installed:
pct exec <CTID> -- which jq - Install jq if needed:
pct exec <CTID> -- apk add jq
Rollback
If something goes wrong:
-
Stop new container:
ssh root@192.168.11.11 "pct stop <NEW_CTID>" -
Start old NPM:
ssh root@192.168.11.11 "pct start 105" -
Update port forwarding back to old IP:
- UDM Pro → Port Forwarding → Update to
192.168.11.26
- UDM Pro → Port Forwarding → Update to
What's Different in NPMplus?
- ✅ HTTP/3 (QUIC) - Faster connections
- ✅ CrowdSec IPS - Intrusion prevention
- ✅ GoAccess - Real-time log analysis
- ✅ ModSecurity - Web application firewall
- ✅ OCSP Stapling - Better SSL performance
- ✅ TLS 1.2/1.3 Only - Enhanced security
- ✅ Faster Certificates - Quicker SSL issuance
Full Documentation
See docs/04-configuration/NPMPLUS_MIGRATION_GUIDE.md for complete details.
Ready to migrate? Start with Step 1 above! 🚀