# Password Setup Guide for VMIDs 2400-2402

**Date**: 2026-01-05  
**Status**: Manual Password Setup Required

---

## Current Situation

✅ **VMs are reachable**: IPs 192.168.11.240-242 are online and SSH ports are open  
❌ **No remote access**: Cannot set passwords remotely without existing credentials  
✅ **Password generated**: `feeO4j9QwpuMgb6dMHi4T2etn`  
✅ **SSH key ready**: `~/.ssh/proxmox_translator`

---

## Setup Instructions

### Step 1: Access Each VM via Console

You need to access each VMID (2400, 2401, 2402) via console to set the root password.

#### Option A: Via Proxmox Web UI

1. Open Proxmox Web UI: https://192.168.11.11:8006
2. Find each VMID (2400, 2401, 2402) - they may be on a different node
3. Click on the VM → Console
4. Login as root (use existing password or console access)

#### Option B: Via Direct Console Access

If you have physical/console access to the VMs, use that.

#### Option C: Check if VMs are on Different Node

The VMs might be on `r630-02` or `ml110`:
```bash
ssh root@192.168.11.11 "for NODE in r630-01 r630-02 ml110; do echo '=== $NODE ==='; qm list | grep -E '2400|2401|2402' || pct list | grep -E '2400|2401|2402'; done"
```

### Step 2: Set Root Password

Once you have console access to each VM, run:

```bash
echo 'root:feeO4j9QwpuMgb6dMHi4T2etn' | chpasswd
```

**Or interactively:**
```bash
passwd root
# Enter: feeO4j9QwpuMgb6dMHi4T2etn
# Confirm: feeO4j9QwpuMgb6dMHi4T2etn
```

### Step 3: Configure SSH Keys (Automated)

After passwords are set, run from your machine:

```bash
# Copy SSH key to each VMID
sshpass -p 'feeO4j9QwpuMgb6dMHi4T2etn' ssh-copy-id -i ~/.ssh/proxmox_translator.pub root@192.168.11.240
sshpass -p 'feeO4j9QwpuMgb6dMHi4T2etn' ssh-copy-id -i ~/.ssh/proxmox_translator.pub root@192.168.11.241
sshpass -p 'feeO4j9QwpuMgb6dMHi4T2etn' ssh-copy-id -i ~/.ssh/proxmox_translator.pub root@192.168.11.242
```

**Or use the automated script:**
```bash
/tmp/setup-ssh-access.sh
```

### Step 4: Verify SSH Access

```bash
# Test each VMID
ssh -i ~/.ssh/proxmox_translator root@192.168.11.240 "echo '✅ 2400 working'"
ssh -i ~/.ssh/proxmox_translator root@192.168.11.241 "echo '✅ 2401 working'"
ssh -i ~/.ssh/proxmox_translator root@192.168.11.242 "echo '✅ 2402 working'"
```

---

## Quick Setup Script

After setting passwords via console, run:

```bash
PASSWORD="feeO4j9QwpuMgb6dMHi4T2etn"
SSH_KEY="$HOME/.ssh/proxmox_translator.pub"

for IP in 192.168.11.240 192.168.11.241 192.168.11.242; do
  echo "Configuring $IP..."
  sshpass -p "$PASSWORD" ssh-copy-id -i "$SSH_KEY" root@$IP
done
```

---

## After SSH is Configured

Once SSH key authentication works, deploy the translator:

```bash
cd /home/intlc/projects/proxmox/rpc-translator-138
/tmp/complete-deployment.sh
```

This will automatically:
1. Deploy translator to all VMIDs
2. Configure .env files
3. Start services
4. Verify everything

---

## Password Reference

- **Password**: `feeO4j9QwpuMgb6dMHi4T2etn`
- **Saved to**: `/tmp/vmid-root-password.txt`
- **SSH Key**: `~/.ssh/proxmox_translator`
- **SSH Public Key**: `~/.ssh/proxmox_translator.pub`

---

## Troubleshooting

### If Console Access Doesn't Work

1. **Check VM status on all nodes:**
   ```bash
   ssh root@192.168.11.11 "for NODE in r630-01 r630-02 ml110; do echo '=== $NODE ==='; qm list | grep -E '2400|2401|2402'; done"
   ```

2. **Check if VMs are LXC containers:**
   ```bash
   ssh root@192.168.11.11 "pct list | grep -E '2400|2401|2402'"
   ```

3. **Try direct network access:**
   - The VMs are reachable (IPs ping, SSH port open)
   - They may have existing SSH access with a different key/password
   - Check if you have existing SSH keys that work

### If Password Setting Fails

- Ensure you're logged in as root
- Check if `chpasswd` command is available
- Try: `passwd root` (interactive)
- Verify password complexity requirements

---

## Summary

1. ✅ Password generated: `feeO4j9QwpuMgb6dMHi4T2etn`
2. ✅ SSH key ready: `~/.ssh/proxmox_translator`
3. ⏳ **Manual step**: Set password via console on each VM
4. ⏳ **Automated step**: Configure SSH keys (after password is set)
5. ⏳ **Automated step**: Deploy translator (after SSH is configured)

All automated scripts are ready. Once passwords are set via console, the rest is automated.