explorer-monorepo/NETWORK_ISSUES_RESOLVED.md

Network Issues Resolved

Date: 2026-01-21
Status: ✅ FIXES APPLIED - Testing results

---

Issues Identified

❌ Issue 1: Container Cannot Reach Gateway

• Problem: 100% packet loss to 192.168.11.1
• Impact: Blocks all outbound internet access
• Status: ✅ FIXED (ARP cache refresh resolved)

❌ Issue 2: DNS Resolution Failing

• Problem: DNS queries timing out
• Impact: Cannot resolve domain names (Docker Hub, etc.)
• Status: ⏳ FIXING (Added backup DNS servers, container restarted)

❌ Issue 3: Docker Hub Not Accessible

• Problem: Cannot reach registry-1.docker.io
• Impact: Cannot pull Docker images
• Status: ⏳ TESTING (May be DNS or firewall issue)

---

Fixes Applied

Fix 1: ARP Cache Refresh

• Action: Flushed ARP cache and refreshed gateway entry
• Result: ✅ Gateway now reachable

Fix 2: DNS Configuration

• Action: Added backup DNS servers (8.8.8.8)
• Result: ⏳ Testing after container restart

Fix 3: Default Route Verification

• Action: Verified default route uses eth0
• Result: ✅ Route is correct

Fix 4: Container Restart

• Action: Restarted container to apply DNS changes
• Result: ⏳ Testing connectivity

---

Current Status

✅ Working

• Gateway connectivity (192.168.11.1)
• Internet connectivity (8.8.8.8)
• Internal network connectivity (192.168.11.10)

⏳ Testing

• DNS resolution (after container restart)
• Docker Hub connectivity
• Docker image pull

---

Next Steps

1. Wait for container to fully restart (10-30 seconds)
2. Test DNS resolution again
3. Test Docker Hub connectivity
4. Attempt Docker pull with longer timeout
5. If still failing: Check UDM Pro firewall for HTTPS/outbound restrictions

---

UDM Pro Firewall Check

If Docker Hub is still not accessible, check UDM Pro:

1. Access UDM Pro Web UI

2. Go to: Settings → Firewall & Security → Firewall Rules

3. Check for rules that might block:

   • Outbound HTTPS (port 443)
   • Outbound traffic from 192.168.11.166/167
   • DNS queries (port 53)

4. Add allow rules if needed:

   • Allow outbound HTTPS from container IPs
   • Allow outbound DNS from container IPs

---

Alternative Solutions

If Docker Pull Still Fails

Option 1: Pull from Proxmox Host

# On Proxmox host (r630-01)
docker pull zoeyvid/npmplus:2026-01-20-r2
docker save zoeyvid/npmplus:2026-01-20-r2 | \
  pct exec 10233 -- docker load

Option 2: Use Proxy/Mirror

• Configure Docker to use a proxy
• Or use a Docker registry mirror

Option 3: Manual Image Transfer

• Download image on a machine with internet
• Transfer to Proxmox host
• Load into container's Docker

---

Summary

Status: ⏳ FIXES APPLIED - TESTING

Progress:

• ✅ Gateway connectivity fixed
• ✅ Internet connectivity working
• ⏳ DNS resolution testing
• ⏳ Docker Hub connectivity testing

Action: Wait for test results, then proceed with Docker pull

---

Next Step: Test DNS and Docker Hub connectivity after container restart