proxmox/docs/09-troubleshooting/R630-04-CONSOLE-ACCESS-GUIDE.md

R630-04 Console Access Guide

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

IP: 192.168.11.14
Tasks: Reset password, fix pveproxy, verify web interface.

---

Step 1: Login via Console

Log in to R630-04 using your console access (physical keyboard, iDRAC KVM, etc.)

---

Step 2: Check Current Status

Once logged in, run these commands to understand the current state:

# Check hostname
hostname
cat /etc/hostname

# Check Proxmox version
pveversion

# Check pveproxy service status
systemctl status pveproxy --no-pager -l

# Check recent pveproxy logs
journalctl -u pveproxy --no-pager -n 50

# Check if port 8006 is listening
ss -tlnp | grep 8006

---

Step 3: Reset Root Password

Set a password for root (you can use L@kers2010 to match other hosts, or choose a different one):

passwd root
# Enter new password twice when prompted

Recommended: Use L@kers2010 to match R630-03 and ml110 for consistency.

---

Step 4: Fix pveproxy Service

4.1 Check Service Status

systemctl status pveproxy --no-pager -l | head -40

4.2 Check Logs for Errors

journalctl -u pveproxy --no-pager -n 100 | grep -i error
journalctl -u pveproxy --no-pager -n 100 | tail -50

4.3 Restart pveproxy

systemctl restart pveproxy
sleep 3
systemctl status pveproxy --no-pager | head -20

4.4 Check if Port 8006 is Now Listening

ss -tlnp | grep 8006

Should show something like:

LISTEN 0      128         0.0.0.0:8006      0.0.0.0:*    users:(("pveproxy",pid=1234,fd=6))

---

Step 5: If pveproxy Still Fails

5.1 Check All Proxmox Services

systemctl list-units --type=service --all | grep -E 'pveproxy|pvedaemon|pve-cluster|pvestatd'
systemctl status pvedaemon --no-pager | head -20
systemctl status pve-cluster --no-pager | head -20

5.2 Restart All Proxmox Services

systemctl restart pveproxy pvedaemon pvestatd pve-cluster
sleep 5
systemctl status pveproxy --no-pager | head -20

5.3 Check for Port Conflicts

# Check if something else is using port 8006
lsof -i :8006
ss -tlnp | grep 8006

5.4 Check Disk Space

df -h
# Low disk space can cause service issues

5.5 Check Log Directory Permissions

ls -la /var/log/pveproxy/
# Should be owned by root:root

5.6 Check Proxmox Cluster Status (if in cluster)

pvecm status

---

Step 6: Verify Web Interface Works

6.1 Test Locally

# Test HTTPS connection locally
curl -k https://localhost:8006 | head -20

# Should return HTML (Proxmox login page)

6.2 Test from Another Host

From another machine on the network:

# Test from R630-03 or your local machine
curl -k https://192.168.11.14:8006 | head -20

6.3 Open in Browser

Open in web browser:

https://192.168.11.14:8006

You should see the Proxmox login page.

---

Step 7: Document Password

Once password is set and everything works, document it:

1. Update docs/PROXMOX_HOST_PASSWORDS.md with R630-04 password
2. Update INFRASTRUCTURE_OVERVIEW_COMPLETE.md with correct status

---

Quick Command Reference

Copy-paste these commands in order:

# 1. Check status
hostname
pveversion
systemctl status pveproxy --no-pager -l | head -30

# 2. Reset password
passwd root
# Enter: L@kers2010 (or your chosen password)

# 3. Fix pveproxy
systemctl restart pveproxy
sleep 3
systemctl status pveproxy --no-pager | head -20
ss -tlnp | grep 8006

# 4. If still failing, restart all services
systemctl restart pveproxy pvedaemon pvestatd
systemctl status pveproxy --no-pager | head -20

# 5. Test web interface
curl -k https://localhost:8006 | head -10

---

Expected Results

After completing these steps:

✅ Root password set and documented
✅ pveproxy service running
✅ Port 8006 listening
✅ Web interface accessible at https://192.168.11.14:8006
✅ SSH access working with new password

---

If Issues Persist

If pveproxy still fails after restart:

1. Check for specific error messages:

   journalctl -u pveproxy --no-pager -n 200 | grep -i "error\|fail\|exit"
   

2. Check Proxmox installation:

   dpkg -l | grep proxmox
   pveversion -v
   

3. Reinstall pveproxy (if needed):

   apt update
   apt install --reinstall pveproxy
   systemctl restart pveproxy
   

4. Check system resources:

   free -h
   df -h
   top -bn1 | head -20
   

---

Once you're done, let me know:

1. What password you set
2. Whether pveproxy is working
3. If the web interface is accessible
4. Any error messages you encountered

I'll update the documentation accordingly!