Proxmox from your phone: what's worth doing, and what to leave at the desk

Proxmox is the quiet workhorse under a lot of homelabs. It runs your VMs and containers, and most of the time you never touch it. But things do come up while you are away from the desk, a VM that needs a nudge, a nagging worry about whether the host is even still up, and it is genuinely useful to handle those from your pocket.

The trick is knowing which jobs suit a phone and which ones do not.

Worth doing from a phone

• Checking the host is alive. A glance at whether the node is up and reachable is the single most reassuring thing you can do while out.
• Seeing what is running. Which VMs and containers are up, which are stopped, and roughly how hard the box is working.
• Starting or stopping a guest. Rebooting a VM that has wedged, or bringing one up you forgot to start, is a tap and perfectly safe.
• Watching resource pressure. CPU, memory, and storage headroom tell you whether you are about to have a problem before you actually do.

Better left at the desk

Some things want a big screen and your full attention. Doing them one-handed on mobile is asking for a bad afternoon.

• Editing storage, or messing with disks and pools.
• Cluster changes, adding or removing nodes.
• Anything touching the network config of the host itself.
• Restoring from backup, where one wrong pick has real consequences.

Why the distinction matters

The failure mode for phone administration is not that you cannot do something. It is that you can, and you do it too fast, on too small a screen, without the context you would have at a desk. So the healthy split is simple: use the phone to observe and to nudge, and use a real screen for anything that changes the shape of the setup.

Read-only reassurance and a couple of safe controls cover almost everything you actually reach for when you are out. The heavy, irreversible work can wait ten minutes until you are back in front of a keyboard, and it should.