123 lines
3.1 KiB
Markdown
123 lines
3.1 KiB
Markdown
# Net1 Removed - Issue Analysis
|
|
|
|
**Date**: 2026-01-21
|
|
**Status**: ⚠️ **ISSUE** - 192.168.11.166 still not accessible after net1 removal
|
|
|
|
---
|
|
|
|
## Current Situation
|
|
|
|
### Configuration
|
|
- ✅ **net1 removed**: Container now has only eth0 (192.168.11.166)
|
|
- ✅ **Docker network**: Bridge mode with port mappings
|
|
- ✅ **docker-proxy**: Listening on 0.0.0.0:80/443/81
|
|
- ✅ **Routing**: Clean (only eth0 route)
|
|
- ❌ **192.168.11.166**: Not accessible (HTTP 000)
|
|
- ⚠️ **Docker container**: Starting (health: starting)
|
|
|
|
---
|
|
|
|
## Analysis
|
|
|
|
### What's Working
|
|
1. **Container network**: Clean single interface (eth0)
|
|
2. **Docker port mappings**: Correct (0.0.0.0:80/443/81)
|
|
3. **docker-proxy**: Running and listening
|
|
|
|
### What's Not Working
|
|
1. **192.168.11.166**: Not accessible from outside
|
|
2. **localhost:80**: Not accessible from inside container
|
|
3. **Docker container health**: Starting (may need more time)
|
|
|
|
---
|
|
|
|
## Possible Causes
|
|
|
|
### 1. NPMplus Not Fully Started
|
|
- Container health shows "starting"
|
|
- NPMplus may need more time to initialize
|
|
- Nginx inside container may not be running yet
|
|
|
|
### 2. Docker Container Internal Issue
|
|
- NPMplus nginx may not be listening inside container
|
|
- Container may be in unhealthy state
|
|
- Need to check container logs
|
|
|
|
### 3. Network Namespace Issue
|
|
- Docker bridge network may have routing issues
|
|
- Port forwarding may not be working correctly
|
|
- Need to verify iptables rules
|
|
|
|
---
|
|
|
|
## Diagnostic Steps
|
|
|
|
### Step 1: Wait for Container to Fully Start
|
|
```bash
|
|
# Wait 30-60 seconds for NPMplus to fully initialize
|
|
# Check health status
|
|
docker ps --filter name=npmplus --format "{{.Status}}"
|
|
```
|
|
|
|
### Step 2: Check NPMplus Processes
|
|
```bash
|
|
docker exec npmplus ps aux | grep nginx
|
|
docker exec npmplus ps aux | grep node
|
|
```
|
|
|
|
### Step 3: Check NPMplus Logs
|
|
```bash
|
|
docker logs npmplus --tail 50
|
|
```
|
|
|
|
### Step 4: Test Direct Connection to Docker Container IP
|
|
```bash
|
|
# Get container IP
|
|
docker inspect npmplus --format "{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}"
|
|
|
|
# Test connection
|
|
curl -I http://<container-ip>:80
|
|
```
|
|
|
|
### Step 5: Check Docker Network
|
|
```bash
|
|
docker network inspect bridge
|
|
docker port npmplus
|
|
```
|
|
|
|
---
|
|
|
|
## Recommended Actions
|
|
|
|
### Immediate
|
|
1. **Wait 30-60 seconds** for NPMplus to fully start
|
|
2. **Check container health** status
|
|
3. **Review container logs** for errors
|
|
|
|
### If Still Not Working
|
|
1. **Check NPMplus nginx** is running inside container
|
|
2. **Verify Docker port mappings** are correct
|
|
3. **Test direct connection** to Docker container IP (172.17.0.2)
|
|
4. **Check iptables rules** for port forwarding
|
|
|
|
### Alternative Solution
|
|
If 192.168.11.166 continues to have issues:
|
|
- **Re-add net1** temporarily
|
|
- **Use 192.168.11.167** (which was working)
|
|
- **Update UDM Pro** to use 192.168.11.167
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. ✅ Wait for container to fully start (30-60 seconds)
|
|
2. ✅ Check NPMplus processes and logs
|
|
3. ✅ Test direct connection to Docker container IP
|
|
4. ✅ If still failing, consider re-adding net1 or investigating Docker networking
|
|
|
|
---
|
|
|
|
**Status**: ⏳ **WAITING** - Container may need more time to fully start
|
|
|
|
**Action**: Wait and re-test, then check container logs if still failing
|