# R630-04 Proxmox Troubleshooting Guide

**IP Address:** 192.168.11.14  
**Proxmox Version:** 6.17.2-1-PVE  
**Issue:** pveproxy worker exit (web interface not accessible on port 8006)

---

## Problem Summary

- Proxmox VE is installed (version 6.17.2-1-PVE)
- SSH access works (port 22)
- Web interface not accessible (port 8006)
- pveproxy workers are crashing/exiting

---

## Diagnostic Steps

### 1. Check pveproxy Service Status

```bash
systemctl status pveproxy --no-pager -l
```

Look for:
- Service state (should be "active (running)")
- Worker process exits
- Error messages

### 2. Check Recent Logs

```bash
journalctl -u pveproxy --no-pager -n 100
```

Look for:
- Worker exit messages
- Error patterns
- Stack traces

### 3. Check Port 8006

```bash
ss -tlnp | grep 8006
# or
netstat -tlnp | grep 8006
```

Should show pveproxy listening on port 8006.

### 4. Check Proxmox Cluster Status

```bash
pvecm status
```

If in a cluster, verify cluster connectivity.

---

## Common Fixes

### Fix 1: Restart pveproxy Service

```bash
systemctl restart pveproxy
systemctl status pveproxy
```

### Fix 2: Check and Fix Configuration

```bash
# Check configuration files
ls -la /etc/pveproxy/
cat /etc/default/pveproxy 2>/dev/null

# Check for syntax errors
pveproxy --help
```

### Fix 3: Reinstall pveproxy Package

```bash
apt update
apt install --reinstall pveproxy
systemctl restart pveproxy
```

### Fix 4: Check for Port Conflicts

```bash
# Find what's using port 8006
ss -tlnp | grep 8006
lsof -i :8006

# If something else is using it, stop that service
```

### Fix 5: Check Disk Space and Permissions

```bash
# Check disk space
df -h

# Check log directory permissions
ls -la /var/log/pveproxy/
# Should be owned by root:root with appropriate permissions
```

### Fix 6: Check for Corrupted Database

```bash
# Check Proxmox database
pveversion -v

# Check cluster database (if in cluster)
systemctl status pve-cluster
```

### Fix 7: Full Service Restart

```bash
# Restart all Proxmox services
systemctl restart pveproxy pvedaemon pvestatd pve-cluster
systemctl status pveproxy pvedaemon pvestatd pve-cluster
```

---

## Advanced Troubleshooting

### View Real-time Logs

```bash
journalctl -u pveproxy -f
```

### Check Worker Process Details

```bash
# See running pveproxy processes
ps aux | grep pveproxy

# Check process limits
cat /proc/$(pgrep -f pveproxy | head -1)/limits
```

### Test pveproxy Manually

```bash
# Stop service
systemctl stop pveproxy

# Try running manually to see errors
/usr/bin/pveproxy start
```

---

## Scripts Available

1. **check-r630-04-commands.sh** - Diagnostic commands
2. **fix-r630-04-pveproxy.sh** - Automated fix script

---

## Expected Resolution

After fixing:
- `systemctl status pveproxy` should show "active (running)"
- `ss -tlnp | grep 8006` should show pveproxy listening
- Web interface should be accessible at `https://192.168.11.14:8006`

---

## Additional Resources

- Proxmox VE Documentation: https://pve.proxmox.com/pve-docs/
- Proxmox Forum: https://forum.proxmox.com/
- Log locations:
  - `/var/log/pveproxy/access.log`
  - `/var/log/pveproxy/error.log`
  - `journalctl -u pveproxy`

