Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
4.8 KiB
4.8 KiB
NPMplus Port Forwarding Configuration Guide
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2026-01-16
Status: Configuration Required
NPMplus IP: 192.168.0.166
Public IP: 76.53.10.36
Overview
Port forwarding must be configured in UDM Pro to route traffic from the public IP to NPMplus. Currently, ports 80 and 443 are not accessible, which prevents Let's Encrypt from validating domains for SSL certificates.
Current Status
✅ DNS Configuration: All 19 domains correctly point to 76.53.10.36
❌ Port Forwarding: Not configured (ports 80/443 not accessible)
Required Port Forwarding Rules
Rule 1: HTTP (Port 80)
- Name: NPMplus HTTP
- Public IP:
76.53.10.36 - Public Port:
80 - Internal IP:
192.168.0.166 - Internal Port:
80 - Protocol:
TCP - Interface: WAN (or appropriate interface)
Rule 2: HTTPS (Port 443)
- Name: NPMplus HTTPS
- Public IP:
76.53.10.36 - Public Port:
443 - Internal IP:
192.168.0.166 - Internal Port:
443 - Protocol:
TCP - Interface: WAN (or appropriate interface)
Manual Configuration Steps
Step 1: Access UDM Pro
- Open web browser
- Navigate to UDM Pro web interface (typically
https://192.168.1.1or your UDM Pro IP) - Log in with admin credentials
Step 2: Navigate to Port Forwarding
- Click Settings (gear icon)
- Go to Firewall & Security
- Click Port Forwarding (or Port Forwarding Rules)
Step 3: Create HTTP Rule
- Click Add Port Forwarding Rule (or Create New Rule)
- Configure:
- Name:
NPMplus HTTP - Source:
Any(or specific IP if needed) - Destination IP:
76.53.10.36 - Destination Port:
80 - Forward to IP:
192.168.0.166 - Forward to Port:
80 - Protocol:
TCP - Interface:
WAN(or your internet-facing interface)
- Name:
- Click Save or Apply
Step 4: Create HTTPS Rule
- Click Add Port Forwarding Rule again
- Configure:
- Name:
NPMplus HTTPS - Source:
Any(or specific IP if needed) - Destination IP:
76.53.10.36 - Destination Port:
443 - Forward to IP:
192.168.0.166 - Forward to Port:
443 - Protocol:
TCP - Interface:
WAN(or your internet-facing interface)
- Name:
- Click Save or Apply
Step 5: Verify Configuration
- Review both rules in the Port Forwarding list
- Ensure they are Enabled
- Check that IPs and ports are correct
Update Existing Rules
If port forwarding rules already exist but point to the old NPM IP (192.168.11.26):
- Find the existing rules (may be named "Nginx" or "NPM")
- Edit each rule
- Update Forward to IP from
192.168.11.26to192.168.0.166 - Save changes
Verification
After configuring port forwarding, verify connectivity:
# Test HTTP
curl -I http://76.53.10.36
# Test HTTPS
curl -I -k https://76.53.10.36
# Test specific domain
curl -I http://sankofa.nexus
Expected: Should return HTTP response (200, 301, 302, etc.) instead of connection timeout.
Troubleshooting
Ports Still Not Accessible
- Check Firewall Rules: Ensure firewall allows traffic on ports 80/443
- Check Interface: Verify WAN interface is correct
- Check IP Assignment: Confirm
76.53.10.36is assigned to UDM Pro WAN interface - Check ISP: Some ISPs block ports 80/443 - may need to use alternate ports
Let's Encrypt Still Failing
- Wait for DNS Propagation: DNS changes can take 5-10 minutes
- Check DNS Resolution: Verify domains resolve to
76.53.10.36from external DNSdig sankofa.nexus @8.8.8.8 - Test HTTP Access: Ensure
http://sankofa.nexusis accessible from internet - Check NPMplus Logs: Review certificate request errors in NPMplus
Next Steps After Port Forwarding
- Wait 5-10 minutes for configuration to take effect
- Test connectivity using curl commands above
- Request SSL certificates in NPMplus:
- Access:
https://192.168.0.166:81 - Go to SSL Certificates
- Click Request New Certificate
- Select domain and request Let's Encrypt certificate
- Access:
- Or use automation script:
bash scripts/request-npmplus-certificates.sh
Architecture
Internet
↓
Cloudflare DNS (76.53.10.36)
↓
UDM Pro Port Forwarding
├─ 76.53.10.36:80 → 192.168.0.166:80
└─ 76.53.10.36:443 → 192.168.0.166:443
↓
NPMplus (192.168.0.166:80/443)
↓
Backend Services (by hostname)