explorer-monorepo/NET1_REMOVAL_RESULT.md

Net1 Removal Result

Date: 2026-01-21
Action: Removed net1 (eth1) from NPMplus container
Result: ⚠️ ISSUE - 192.168.11.166 still not accessible

---

Current Status

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
• ❌ 192.168.11.166: Not accessible (HTTP 000)
• ⚠️ Docker container: Running but unhealthy

Issue

NPMplus Docker container is not responding:

• Container status: Running but unhealthy
• Not accessible on 192.168.11.166
• Not accessible on Docker container IP (172.17.0.2)
• Not accessible on localhost from inside container

---

Root Cause Analysis

Possible Causes

1. NPMplus Not Fully Started

   • Container health shows "unhealthy"
   • May need more time to initialize
   • Health checks may be failing

2. Data Volume Issue

   • Volume path is correct: /data/npmplus:/data
   • Both /opt/npmplus and /data/npmplus exist
   • May need to verify data is accessible

3. Docker Container Configuration

   • Container is running but not responding
   • NPMplus nginx may not be starting
   • Need to check container logs for errors

4. Network Namespace Issue

   • Docker bridge network may have issues
   • Port forwarding may not be working
   • Need to verify iptables rules

---

Immediate Solution

Re-add net1 to Restore Functionality

Since removing net1 broke access and NPMplus container is not responding:

1. Re-add net1 to restore 192.168.11.167 access
2. Update UDM Pro to use 192.168.11.167
3. Investigate Docker container issue separately

Script created: scripts/re-add-net1.sh

---

Recommended Actions

Option 1: Re-add net1 (Quick Fix)

bash scripts/re-add-net1.sh

This will:

• Re-add net1 (eth1) with IP 192.168.11.167
• Restart container
• Restore functionality on 192.168.11.167

Option 2: Fix Docker Container First

1. Check NPMplus container logs for errors
2. Verify data volume is accessible
3. Check if NPMplus nginx is starting
4. Fix container health issues
5. Then test 192.168.11.166 again

Option 3: Use Different Approach

• Keep net1 removed
• Fix Docker container health
• Once container is healthy, test 192.168.11.166
• If still not working, re-add net1

---

Next Steps

1. Immediate: Re-add net1 to restore functionality
2. Short-term: Update UDM Pro to use 192.168.11.167
3. Long-term: Investigate and fix Docker container health issue
4. Future: Once Docker container is fixed, can remove net1 again

---

Summary

Status: ⚠️ NET1 REMOVAL CAUSED ISSUE

Problem:

• Removing net1 did not fix 192.168.11.166 accessibility
• NPMplus Docker container is unhealthy and not responding
• No access on any IP

Solution:

• Re-add net1 to restore 192.168.11.167 access
• Update UDM Pro port forwarding
• Investigate Docker container separately

Action: Run scripts/re-add-net1.sh to restore functionality

---

Next Step: Re-add net1 to restore access, then investigate Docker container health