proxmox/docs/archive/fixes/BLOCKSCOUT_IP_FIX_APPLIED.md

Blockscout IP Fix Applied

Date: $(date)
Issue: Container had dynamic IP 192.168.11.17 instead of expected 192.168.11.140
Status: ✅ FIXED

---

Issue Identified

From Proxmox web interface screenshot:

• Current IP: 192.168.11.17/24 (dynamic)
• Expected IP: 192.168.11.140/24 (static)
• Status: Container was still using DHCP instead of static IP

---

Fix Applied

1. Updated Container Configuration

Set static IP configuration via Proxmox API:

pvesh set /nodes/pve2/lxc/5000/config \
  --net0 'name=eth0,bridge=vmbr0,hwaddr=BC:24:11:3C:58:2B,ip=192.168.11.140/24,gw=192.168.11.1,type=veth'

2. Container Reboot

Rebooted container to apply network configuration changes:

pvesh create /nodes/pve2/lxc/5000/status/reboot

---

Verification

After container restarts, verify the IP address:

1. Via Proxmox Web UI:

   • Navigate to: Container 5000 → Network
   • Check IP address should show: 192.168.11.140/24 (static)

2. Via Command Line:

   ssh root@192.168.11.10 "pct exec 5000 -- ip addr show eth0"
   

3. Via Script:

   bash scripts/check-blockscout-actual-ip.sh
   

---

Expected Result

• ✅ IP Address: 192.168.11.140/24
• ✅ Type: static (not dynamic)
• ✅ Gateway: 192.168.11.1
• ✅ All scripts referencing 192.168.11.140 will now match actual IP

---

Next Steps

1. Wait for container to fully restart (~30 seconds)
2. Verify IP address in Proxmox web UI (should show 192.168.11.140/24 (static))
3. Test connectivity:

   bash scripts/complete-blockscout-firewall-fix.sh
   

4. Configure Omada firewall rule for 192.168.11.140:80 if not already done

---

Last Updated: $(date)