Runbook · Maxedge

Cannot SSH into Maxedge

Access

Symptom

Connection refused / timeout / permission denied on 192.168.30.111.

Investigate

Are you on the right VLAN (service port 12, VLAN 99)? Can you ping the VM? Permission denied usually means wrong key or key permissions.

Fix

chmod 600 ~/.ssh/maxedge_key
ssh -v -i ~/.ssh/maxedge_key maxedge@192.168.30.111
# VM down? Check Proxmox:
# https://192.168.30.110:8006 -> node -> VM maxedge -> Start

Keys are per-unit — always fetch the current key from Vault → lh/maxedge/ssh; old keys are rotated out.

Steps

Timeout: check your address — must be 192.168.99.x (port 12, DHCP). On 192.168.30.x or Wi-Fi → wrong port / bridged. See service laptop checklist.
ping 192.168.30.111. No reply → VM down; open Proxmox https://192.168.30.110:8006 and start VM maxedge (host runbook).
Connection refused with ping OK → VM booting or sshd down; wait 2 min, then check from the Proxmox console.
Permission denied: fetch the current key from Vault lh/maxedge/ssh, chmod 600, connect with -v to see which key is offered.
Remote instead of on site? Use an eHawk session — same key.

Not resolved? Escalate to Product Engineering with docker ps -a, the relevant docker logs and the unit's Masterdata link.