133 lines
2.7 KiB
Markdown
133 lines
2.7 KiB
Markdown
|
# NPMplus Installation Error Fix
|
||
|
|
|
||
|
|
**Last Updated:** 2026-01-31
|
||
|
|
**Document Version:** 1.0
|
||
|
|
**Status:** Active Documentation
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Error**: `no configuration file provided: not found`
|
||
|
|
**When**: Running `docker compose pull` during NPMplus installation
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Problem
|
||
|
|
|
||
|
|
The Proxmox helper script tries to run `docker compose pull` before ensuring:
|
||
|
|
1. The script is in the `/opt` directory
|
||
|
|
2. The `compose.yaml` file exists
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Solutions
|
||
|
|
|
||
|
|
### Solution 1: Fix Existing Container (if one was created)
|
||
|
|
|
||
|
|
If a container was partially created, fix it:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
# Find the container ID
|
||
|
|
ssh root@192.168.11.11 "pct list | tail -5"
|
||
|
|
|
||
|
|
# Fix the installation
|
||
|
|
bash scripts/nginx-proxy-manager/fix-npmplus-install.sh 192.168.11.11 <CONTAINER_ID>
|
||
|
|
```
|
||
|
|
|
||
|
|
### Solution 2: Re-run Installation with Fix
|
||
|
|
|
||
|
|
Use the fixed installation script:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
bash scripts/nginx-proxy-manager/install-npmplus-fixed.sh
|
||
|
|
```
|
||
|
|
|
||
|
|
### Solution 3: Manual Fix After Installation
|
||
|
|
|
||
|
|
If installation partially completed:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
ssh root@192.168.11.11
|
||
|
|
pct enter <CONTAINER_ID>
|
||
|
|
|
||
|
|
# Ensure we're in /opt
|
||
|
|
cd /opt
|
||
|
|
|
||
|
|
# Download compose.yaml if missing
|
||
|
|
if [ ! -f compose.yaml ]; then
|
||
|
|
curl -fsSL "https://raw.githubusercontent.com/ZoeyVid/NPMplus/refs/heads/develop/compose.yaml" -o compose.yaml
|
||
|
|
fi
|
||
|
|
|
||
|
|
# Update with your settings
|
||
|
|
yq -i "
|
||
|
|
.services.npmplus.environment |=
|
||
|
|
(map(select(. != \"TZ=*\" and . != \"ACME_EMAIL=*\")) +
|
||
|
|
[\"TZ=America/New_York\", \"ACME_EMAIL=nsatoshi2007@hotmail.com\"])
|
||
|
|
" compose.yaml
|
||
|
|
|
||
|
|
# Start NPMplus
|
||
|
|
docker compose up -d
|
||
|
|
```
|
||
|
|
|
||
|
|
### Solution 4: Use Complete Migration Script
|
||
|
|
|
||
|
|
The complete migration script handles errors automatically:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
bash scripts/nginx-proxy-manager/complete-migration.sh
|
||
|
|
```
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Prevention
|
||
|
|
|
||
|
|
The error occurs because:
|
||
|
|
- The script runs `docker compose` from wrong directory
|
||
|
|
- `compose.yaml` wasn't downloaded successfully
|
||
|
|
- Network issues during installation
|
||
|
|
|
||
|
|
**To prevent:**
|
||
|
|
1. Ensure stable network connection
|
||
|
|
2. Run installation from Proxmox host directly
|
||
|
|
3. Use the fixed installation script
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Verification
|
||
|
|
|
||
|
|
After fixing, verify installation:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
# Check container is running
|
||
|
|
ssh root@192.168.11.11 "pct status <CTID>"
|
||
|
|
|
||
|
|
# Check Docker containers
|
||
|
|
ssh root@192.168.11.11 "pct exec <CTID> -- docker ps"
|
||
|
|
|
||
|
|
# Check compose.yaml exists
|
||
|
|
ssh root@192.168.11.11 "pct exec <CTID> -- ls -la /opt/compose.yaml"
|
||
|
|
|
||
|
|
# Check NPMplus is accessible
|
||
|
|
curl -k https://<container-ip>:81
|
||
|
|
```
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Next Steps
|
||
|
|
|
||
|
|
After fixing the installation:
|
||
|
|
|
||
|
|
1. Get container ID and IP
|
||
|
|
2. Run post-installation migration:
|
||
|
|
```bash
|
||
|
|
bash scripts/nginx-proxy-manager/post-install-migration.sh \
|
||
|
|
192.168.11.11 \
|
||
|
|
<CONTAINER_ID> \
|
||
|
|
<CONTAINER_IP>
|
||
|
|
```
|
||
|
|
3. Update UDM Pro port forwarding
|
||
|
|
4. Test all domains
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**All fix scripts are ready. Use the one that matches your situation.**
|