proxmox/rpc-translator-138/DEPLOYMENT_READY.md

Translator Deployment - Ready to Complete

Date: 2026-01-05
Status: All Automated Steps Complete - Manual SSH Setup Required

---

✅ Completed (100%)

Supporting Infrastructure

• ✅ Redis (VMID 106): Running on 192.168.11.110:6379
• ✅ Web3Signer (VMID 107): Running on 192.168.11.111:9000 (ChainID 138)
• ✅ Vault (VMID 108): Running on 192.168.11.112:8200
• ✅ Project built and ready
• ✅ Deployment scripts updated and ready
• ✅ Configuration scripts ready
• ✅ SSH key generated: ~/.ssh/proxmox_translator

---

⏳ Manual Step Required: SSH Authentication

The translator VMIDs (2400-2402) require SSH authentication setup. This is a one-time manual step.

Your SSH Public Key

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMvpR7yi4+eKHL9e8nPtWVfrEZ6+Z7JCs57SE8IAueTY intlc@ASERET

Quick Setup (Choose One Method)

Method 1: ssh-copy-id (Easiest)

If you have the root password for the VMIDs:

# Copy key to each VMID (will prompt for password once each)
ssh-copy-id -i ~/.ssh/proxmox_translator.pub root@192.168.11.240
ssh-copy-id -i ~/.ssh/proxmox_translator.pub root@192.168.11.241
ssh-copy-id -i ~/.ssh/proxmox_translator.pub root@192.168.11.242

Method 2: Manual Key Installation

If you don't have passwords, access each VMID via Proxmox console/UI and run:

# On each VMID (2400, 2401, 2402)
mkdir -p ~/.ssh
echo "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMvpR7yi4+eKHL9e8nPtWVfrEZ6+Z7JCs57SE8IAueTY intlc@ASERET" >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
chmod 700 ~/.ssh

Method 3: Test Password Authentication

If password authentication works, the deployment scripts will prompt for passwords:

ssh root@192.168.11.240
# Enter password when prompted

---

🚀 After SSH is Configured

Once SSH authentication works, run:

cd /home/intlc/projects/proxmox/rpc-translator-138

# Deploy to all VMIDs (automated)
./scripts/deploy-all-vmids.sh

This will automatically:

1. ✅ Build the project
2. ✅ Copy files to all VMIDs
3. ✅ Install dependencies
4. ✅ Install systemd service

Then configure .env files and start services:

# Configure .env files (automated script)
/tmp/configure-env-all.sh

# Start services (automated script)
/tmp/start-services-all.sh

# Verify everything (automated script)
/tmp/verify-all-services.sh

---

📋 Complete Deployment Checklist

Prerequisites ✅

• Supporting services deployed (Redis, Web3Signer, Vault)
• Project built and ready
• Deployment scripts ready
• SSH key generated

Manual Steps ⏳

• SSH authentication configured (see above)
• Run deployment script
• Verify .env files are configured
• Verify services are running

Automated Steps (After SSH Setup) ✅

• Deployment script ready
• Configuration script ready
• Service startup script ready
• Verification script ready

---

🔧 Troubleshooting

If SSH Key Copy Fails

1. Check SSH service is running on VMIDs:

   # From Proxmox host or via console
   systemctl status ssh
   

2. Check if password authentication is enabled:

   # On each VMID
   grep -E '^PasswordAuthentication|^PubkeyAuthentication' /etc/ssh/sshd_config
   

3. Manually add key via Proxmox console:

   • Access VMID via Proxmox Web UI console
   • Run the manual key installation commands above

If Deployment Script Fails

1. Test SSH access manually:

   ssh -i ~/.ssh/proxmox_translator root@192.168.11.240 "echo 'Success'"
   

2. Check VMID status:

   # From Proxmox host
   qm status 2400
   

3. Check network connectivity:

   ping 192.168.11.240
   

---

📊 Current Status Summary

Component	Status	Notes
Redis	✅ Running	192.168.11.110:6379
Web3Signer	✅ Running	192.168.11.111:9000
Vault	✅ Running	192.168.11.112:8200
Project Build	✅ Complete	Ready in dist/
Deployment Scripts	✅ Ready	Updated for SSH key
SSH Key	✅ Generated	~/.ssh/proxmox_translator
SSH Authorization	⏳ Manual	One-time setup needed
Translator Deployment	⏳ Pending	After SSH setup
Service Configuration	⏳ Pending	After deployment

---

🎯 Next Action

Set up SSH authentication (5 minutes), then run:

cd /home/intlc/projects/proxmox/rpc-translator-138
./scripts/deploy-all-vmids.sh

All supporting infrastructure is complete and operational. The translator deployment can proceed immediately once SSH access is configured.