# Reserved IP Conflicts - Fix Summary

**Date**: 2026-01-02  
**Status**: ✅ **IPs CHANGED** | ⚠️ **STORAGE ISSUE**  
**Reserved Range**: 192.168.11.10 - 192.168.11.25 (Physical Servers)

---

## ✅ IP Addresses Changed

### VMID 105 (nginxproxymanager)
- **Old IP**: 192.168.11.21 ❌ (reserved for physical servers)
- **New IP**: 192.168.11.26 ✅
- **Node**: r630-02
- **IP Change Status**: ✅ **COMPLETE**

### VMID 130 (monitoring-1)
- **Old IP**: 192.168.11.22 ❌ (reserved for physical servers)
- **New IP**: 192.168.11.27 ✅
- **Node**: r630-02
- **IP Change Status**: ✅ **COMPLETE**

---

## ⚠️ Storage Issue

**Problem**: Containers cannot start due to storage configuration issue:
```
no such logical volume pve/thin1
```

**Root Cause**: Storage pool `pve/thin1` is not available on r630-02.

**Impact**: 
- ✅ IP addresses have been changed successfully
- ❌ Containers cannot start until storage is fixed

**Action Required**: Fix storage configuration on r630-02 before starting containers.

---

## About 192.168.11.14

**Question**: Which VMID is responding when pinging 192.168.11.14?

**Answer**: **No VMID** - 192.168.11.14 is the **physical server r630-04**.

**Physical Server Details**:
- **Hostname**: r630-04
- **IP**: 192.168.11.14
- **External IP**: 76.53.10.39
- **Status**: ✅ Reachable (but has SSH password and Proxmox Web UI issues)

This is **correct** - the IP belongs to the physical Proxmox host, not a container.

---

## Reserved IP Range Status

**Range**: 192.168.11.10 - 192.168.11.25

**Status**: ✅ **FREE** - No VMIDs are using this range anymore

**Physical Server Assignments**:
- 192.168.11.10 → ml110
- 192.168.11.11 → r630-01
- 192.168.11.12 → r630-02
- 192.168.11.13 → r630-03
- 192.168.11.14 → r630-04
- 192.168.11.15 → r630-05
- 192.168.11.16-25 → Reserved for future physical servers

---

## Next Steps

### 1. Fix Storage on r630-02 (Priority)

The containers need storage to be fixed before they can start:

```bash
# Check available storage
ssh root@192.168.11.12 "pvesm status"

# Check storage configuration for containers
ssh root@192.168.11.12 "pct config 105 | grep rootfs"
ssh root@192.168.11.12 "pct config 130 | grep rootfs"

# Fix storage or migrate to available storage pool
```

**Reference**: See `docs/PROXMOX_CLUSTER_STORAGE_STATUS_REPORT.md` for storage configuration.

### 2. Start Containers (After Storage Fix)

```bash
# Start containers once storage is fixed
ssh root@192.168.11.12 "pct start 105 && pct start 130"

# Verify they're running
ssh root@192.168.11.12 "pct list | grep -E '105|130'"
```

### 3. Update Configuration Files

Update any references to the old IPs:

**Old IPs** → **New IPs**:
- 192.168.11.21 → 192.168.11.26 (nginxproxymanager)
- 192.168.11.22 → 192.168.11.27 (monitoring-1)

**Files to update**:
- DNS records
- Firewall rules
- Service configurations
- Monitoring configurations
- Cloudflare tunnel routes (if applicable)

### 4. Test Services

After containers are running:

```bash
# Test Nginx Proxy Manager
curl -k https://192.168.11.26:8443

# Test Monitoring
curl -k https://192.168.11.27:3000  # (adjust port as needed)
```

---

## Verification

### Verify IP Changes

```bash
# Check VMID 105
ssh root@192.168.11.12 "pct config 105 | grep net0"
# Expected: ip=192.168.11.26/24

# Check VMID 130
ssh root@192.168.11.12 "pct config 130 | grep net0"
# Expected: ip=192.168.11.27/24
```

### Verify Reserved Range is Free

```bash
# Run the check script
./scripts/find-reserved-ip-conflicts.sh
# Should show: ✅ No VMIDs found using reserved IP range
```

---

## Summary

✅ **IP Conflicts Fixed**:
- VMID 105: 192.168.11.21 → 192.168.11.26
- VMID 130: 192.168.11.22 → 192.168.11.27

✅ **Reserved Range Free**: 192.168.11.10-25 is now exclusively for physical servers

✅ **192.168.11.14**: Correctly identified as physical server r630-04 (not a VMID)

⚠️ **Storage Issue**: Containers need storage fix before they can start

---

**Last Updated**: 2026-01-02  
**Fix Script**: `scripts/fix-reserved-ip-conflicts.sh`  
**Status**: IPs changed ✅ | Storage fix needed ⚠️
