explorer-monorepo/PUBLIC_IP_CONNECTIVITY_TEST.md

Public IP Connectivity Test Results

Date: 2026-01-21
Public IP: 76.53.10.36
Test Method: Direct IP access (bypassing DNS)

---

Test Results

Port Connectivity Tests

Port 80 (HTTP)

• Test: Direct connection to 76.53.10.36:80
• Result: [See test output below]
• Status: ⚠️ TIMEOUT or ✅ CONNECTED

Port 443 (HTTPS)

• Test: Direct connection to 76.53.10.36:443
• Result: [See test output below]
• Status: ⚠️ TIMEOUT or ✅ CONNECTED

HTTP/HTTPS Response Tests

HTTP Direct IP

• Test: curl http://76.53.10.36
• Result: [See test output below]

HTTPS Direct IP

• Test: curl https://76.53.10.36
• Result: [See test output below]

HTTP with Host Header

• Test: curl -H "Host: explorer.d-bis.org" http://76.53.10.36
• Result: [See test output below]
• Purpose: Tests if NPMplus responds to correct Host header

HTTPS with Host Header

• Test: curl -H "Host: explorer.d-bis.org" https://76.53.10.36
• Result: [See test output below]
• Purpose: Tests if NPMplus responds to correct Host header

Network Connectivity Tests

Ping Test

• Test: ping -c 4 76.53.10.36
• Result: [See test output below]
• Purpose: Verify basic network connectivity

Traceroute

• Test: traceroute 76.53.10.36
• Result: [See test output below]
• Purpose: See network path to public IP

---

Analysis

If Ports Are Closed/Timeout

Possible Causes:

1. UDM Pro Firewall Blocking

   • Port forwarding rules not enabled
   • Firewall rules blocking WAN → LAN
   • Rule order issue (block before allow)

2. ISP Blocking

   • ISP blocking ports 80/443
   • Common for residential connections
   • May require business connection

3. Network Routing

   • Traffic not reaching UDM Pro
   • WAN interface not receiving traffic
   • ISP routing issue

If Ports Are Open But No Response

Possible Causes:

1. NPMplus Not Responding

   • Service not running
   • Wrong Host header
   • SSL certificate issue

2. Port Forwarding Not Working

   • Rules configured but not active
   • Wrong internal IP
   • Interface mismatch

If Ports Are Open and Responding

Status: ✅ Working!

• External access is functional
• Issue may be DNS-related
• Or browser cache/SSL issue

---

Next Steps Based on Results

If Timeout/Closed:

1. Check UDM Pro port forwarding rules are enabled
2. Verify firewall rule order
3. Test from different network (mobile hotspot)
4. Check ISP restrictions

If Open But No Response:

1. Verify NPMplus is running
2. Check Host header requirement
3. Verify port forwarding destination IP
4. Check NPMplus logs

If Working:

1. Clear browser cache
2. Check DNS resolution
3. Test SSL certificate
4. Verify domain configuration

---

Expected Behavior

If everything is working correctly:

• Port 80: Should respond with HTTP 301 redirect to HTTPS
• Port 443: Should respond with HTTP 200 and explorer frontend
• Host header: Should route to correct backend (VMID 5000)

---

Test Results: [See command output below]