cb47cce074
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
1.5 KiB
1.5 KiB
Fix Proxmox Host Connection
The hostname ml110 is not resolving. Use one of these options:
Option 1: Use IP Address Directly
Find the Proxmox host IP address and use it instead:
# Replace <PROXMOX_IP> with the actual IP address
scp /tmp/web3signer-keys/keystore-*.json root@<PROXMOX_IP>:/tmp/web3signer-keys/
Option 2: Add to /etc/hosts
# Add to /etc/hosts (replace with actual IP)
sudo echo "<PROXMOX_IP> ml110" >> /etc/hosts
Option 3: Use SSH Config
Add to ~/.ssh/config:
Host ml110
HostName <PROXMOX_IP>
User root
Finding the Proxmox Host IP
The Proxmox host should be on the same network as the containers. Based on the container IPs:
- Redis: 192.168.11.110 (VMID 106)
- Web3Signer: 192.168.11.111 (VMID 107)
- Vault: 192.168.11.112 (VMID 108)
The Proxmox host is likely on the same subnet (192.168.11.x).
Common Proxmox host IPs:
- 192.168.11.1 (gateway)
- 192.168.11.10-50 (typical host range)
To find it:
# If you have access to one of the containers, check gateway
ssh root@192.168.11.111 "ip route | grep default"
# Or check your network configuration
ip route | grep 192.168.11
Quick Fix - Use IP Directly
If you know the Proxmox host IP (let's say it's 192.168.11.10):
# Copy keys
scp /tmp/web3signer-keys/keystore-*.json root@192.168.11.10:/tmp/web3signer-keys/
# Load keys
ssh root@192.168.11.10 'bash -s' < /home/intlc/projects/proxmox/rpc-translator-138/scripts/load-keys-complete.sh
Or update the script to use IP instead of hostname.