Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
2.8 KiB
2.8 KiB
Troubleshooting Proxmox Connection
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Current Issue
The Proxmox host 192.168.11.10 is not reachable from this machine.
Diagnosis Results
- ❌ Ping Test: 100% packet loss (host unreachable)
- ❌ Port 8006: Not accessible
- ✅ Configuration: Loaded correctly from
~/.env
Possible Causes
-
Network Connectivity
- Host is on a different network segment
- VPN not connected
- Network routing issue
- Host is powered off
-
Firewall
- Firewall blocking port 8006
- Network firewall rules
-
Wrong Host Address
- Host IP may have changed
- Host may be on different network
Troubleshooting Steps
1. Check Network Connectivity
# Test basic connectivity
ping -c 3 192.168.11.10
# Check if host is on same network
ip route | grep 192.168.11.0
2. Check Alternative Hosts
If you have access to other Proxmox hosts, try:
# Test connectivity to alternative hosts
ping -c 3 <alternative-proxmox-host>
3. Use Shell Script (SSH Alternative)
If you have SSH access to the Proxmox node, use the shell script instead:
export PROXMOX_HOST=192.168.11.10
export PROXMOX_USER=root
./list_vms.sh
The shell script uses SSH which may work even if the API port is blocked.
4. Check VPN/Network Access
If the Proxmox host is on a remote network:
- Ensure VPN is connected
- Verify network routing
- Check if you're on the correct network segment
5. Verify Host is Running
- Check if Proxmox host is powered on
- Verify Proxmox services are running
- Check Proxmox web interface accessibility
6. Test from Proxmox Host Itself
If you can access the Proxmox host directly:
# SSH to Proxmox host
ssh root@192.168.11.10
# Test API locally
curl -k https://localhost:8006/api2/json/version
Alternative: Use Shell Script
The shell script (list_vms.sh) uses SSH instead of the API, which may work even if:
- API port is blocked
- You're on a different network
- VPN provides SSH access but not API access
export PROXMOX_HOST=192.168.11.10
export PROXMOX_USER=root
./list_vms.sh
Next Steps
- If host is accessible via SSH: Use
list_vms.sh - If host is on different network: Connect VPN or update network routing
- If host IP changed: Update
PROXMOX_HOSTin~/.env - If host is down: Wait for it to come back online
Quick Test Commands
# Test ping
ping -c 3 192.168.11.10
# Test port
timeout 5 bash -c "echo > /dev/tcp/192.168.11.10/8006" && echo "Port open" || echo "Port closed"
# Test SSH (if available)
ssh -o ConnectTimeout=5 root@192.168.11.10 "pvesh get /nodes" && echo "SSH works" || echo "SSH failed"
# Check current network
ip addr show | grep "inet "