Files

defiQUG cb47cce074 Complete markdown files cleanup and organization

- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.

2026-01-06 01:46:25 -08:00

2.2 KiB

Raw Permalink Blame History

Blockscout IP Address Verification

Issue: Scripts reference 192.168.11.140 but container uses DHCP

Configuration Source

The IP 192.168.11.140 comes from:

config/network.conf:
```
PUBLIC_START_IP="192.168.11.140"
```

scripts/deployment/deploy-explorer.sh (line 118-119):

ip_octet=140
ip_address="${PUBLIC_SUBNET:-192.168.11}.${ip_octet}"  # = 192.168.11.140

Container Configuration:
- Container VMID 5000 is configured with ip=dhcp
- This means it gets its IP from DHCP, not a static assignment
- The actual IP may differ from 192.168.11.140

Verification

To check the actual IP assigned to Blockscout container:

# Check actual IP
ssh root@192.168.11.10 "pct exec 5000 -- hostname -I"

# Or check via Proxmox API
ssh root@192.168.11.10 "pvesh get /nodes/pve2/lxc/5000/config --output-format json-pretty | grep net0"

Solution Options

Option 1: Verify Actual IP and Update Scripts

If the container has a different IP, update all scripts to use the actual IP:

# Find actual IP
ACTUAL_IP=$(ssh root@192.168.11.10 "pct exec 5000 -- hostname -I | awk '{print \$1}'")

# Update scripts
sed -i "s/192\.168\.11\.140/$ACTUAL_IP/g" scripts/*.sh

Option 2: Configure Static IP Reservation

Configure DHCP server to always assign 192.168.11.140 to the container's MAC address:

Get container MAC address:

ssh root@192.168.11.10 "pvesh get /nodes/pve2/lxc/5000/config --output-format json-pretty | grep hwaddr"

Configure DHCP reservation in Omada Controller or DHCP server

Option 3: Change Container to Static IP

Modify container configuration to use static IP:

ssh root@192.168.11.10 "pct set 5000 --net0 name=eth0,bridge=vmbr0,ip=192.168.11.140/24,gw=192.168.11.1"

Then restart container:

ssh root@192.168.11.10 "pct reboot 5000"

Current Status

Expected IP: 192.168.11.140 (from configuration)
Container Config: ip=dhcp (dynamic assignment)
Actual IP: Unknown (needs verification)

Action Required: Verify actual IP and either:

Update scripts to use actual IP, OR
Configure static IP reservation/assignment

2.2 KiB Raw Permalink Blame History