Legacy/primary home-services Proxmox node; direct verification is currently limited by the documented SSH/name-resolution issue.
| Field | Value |
|---|---|
| Audience | Administrator |
| Public URL | https://proxmox1.pittsfamily.me |
| SSH | ssh proxmox1 is documented but currently unreliable |
| LAN IP | 10.0.2.11 |
| Known guests | HAOS VM 100, media LXC 102, vpn-torrent LXC 103, homelab-ops LXC 101 |
| Verification note | proxmox2 cluster lookup for proxmox1 failed today with hostname lookup errors. |
| Last verified | 2026-06-12 |
proxmox1 hosts long-running home services including Home Assistant and media/ops containers. MCP and the Phase 3 prompt both mark direct SSH to this node as broken or unreliable. During this verification pass, pvesh get /nodes/proxmox1/... from proxmox2 failed with a hostname lookup error, and /etc/pve/nodes/proxmox1 was absent on proxmox2. Treat this page as a runbook plus known-state summary until proxmox1 SSH is repaired.
This page is for administrators only.
Try the UI first:
https://proxmox1.pittsfamily.me.CLI access should use the alias only:
ssh proxmox1
If direct SSH fails, stop after one authentication failure. Do not try guessed usernames, key files, or ports.
Known inventory from MCP and the current support plan:
| Guest | IP | Role |
|---|---|---|
VM 100 haos |
10.0.2.12 | Home Assistant OS |
LXC 101 homelab-ops |
10.0.2.23 | Wiki.js and homelab services |
LXC 102 media |
10.0.2.21 | Prowlarr, Lidarr, Navidrome, Calibre-Web, Uptime Kuma |
LXC 103 vpn-torrent |
10.0.50.10 | Gluetun VPN and qBittorrent |
Public routes currently pointing at proxmox1-hosted services include:
| Public URL | Internal target |
|---|---|
https://homeassistant.pittsfamily.me |
10.0.2.12:8123 |
https://help.pittsfamily.me |
10.0.2.23:3000 |
https://navidrome.pittsfamily.me |
10.0.2.21:4533 |
https://lidarr.pittsfamily.me |
10.0.2.21:8686 |
https://prowlarr.pittsfamily.me |
10.0.2.21:9696 |
https://calibre.pittsfamily.me |
10.0.2.21:8083 |
https://uptime.pittsfamily.me |
10.0.2.21:3001 |
https://torrent.pittsfamily.me |
10.0.50.10:8080 |
ssh proxmox1 'pveversion'
ssh proxmox1 'pct list'
ssh proxmox1 'qm list'
If SSH is still broken, use the Proxmox UI at https://proxmox1.pittsfamily.me. Do not make live changes until you can verify backups and the affected guest.
ssh proxmox1 'pct exec 102 -- bash -lc "docker ps"'
ssh proxmox1 'qm status 100'
Backups should be stored on Mnemosyne-backed Proxmox storage. The most important restore candidates are:
| Guest | Priority | Reason |
|---|---|---|
VM 100 haos |
Critical | Home automation control plane |
LXC 101 homelab-ops |
High | Wiki.js and documentation |
LXC 102 media |
Medium | Media apps and monitoring |
LXC 103 vpn-torrent |
Medium | Isolated VPN/torrent workload |
Verify backup jobs in the Proxmox UI until CLI access is repaired.
10.0.2.11.homelab-ops LXC 101 so help.pittsfamily.me comes back.proxmox2 still point at the correct IPs and ports.proxmox and this wiki page after direct verification succeeds.| Issue | Impact | Current action |
|---|---|---|
| Direct proxmox1 SSH is documented as broken | CLI administration is limited | Use UI and repair SSH in a dedicated maintenance task. |
pvesh fallback from proxmox2 failed today |
Cannot live-query proxmox1 guest status from proxmox2 | Do not pretend this page is fully live-verified. Reverify after DNS/cluster lookup repair. |
| Home Assistant depends on proxmox1 | Node outage affects automations | Keep HAOS backups current and tested. |