Use cases, SSH, SFTP, RDP & VNC for macOS

Proxmox VE management from your Mac

SSH to PVE nodes, noVNC console to guest VMs, SFTP for ISO uploads, Proxmox workflows in one native macOS window.

Proxmox VE is a Debian-based hypervisor that combines KVM virtualization with LXC containers and a clean web UI. Day-to-day, you'll SSH into the PVE nodes (the host OS) for system maintenance, use the noVNC console embedded in the web UI for guest VMs that don't have SSH yet (think Windows installs or rescue boots), upload ISOs via SFTP to `/var/lib/vz/template/iso/`, and run cluster-wide commands across nodes. SSHive handles every piece: SSH/SFTP/VNC out of the box, broadcast for cluster operations, and tunnels to reach the PVE web UI on port 8006 securely.

SSH to PVE nodes

PVE's default user is `root` over SSH (yes, you should add a sudo user). Disable password auth, copy your SSH key. Create a SSHive profile for each node, pve1, pve2, pve3. Group them in a folder. For cluster commands, broadcast to all three: `pveversion`, `qm list`, `pvecm status`. Output side-by-side reveals immediately if a node has fallen out of cluster quorum.

noVNC console for guest VMs

Proxmox embeds noVNC for guest console access, the same protocol SSHive's VNC viewer speaks. To open a guest console outside of the PVE web UI: in PVE web UI, navigate to the VM, Console → "expand", note the URL pattern. Or simpler: query `qm vncproxy <vmid>` over SSH to get a one-time port and password, then connect from SSHive's VNC pane to `pve-host:port`. Useful for VMs without network connectivity yet (fresh installs, rescue boots).

SFTP-upload ISOs

Drag any `.iso` file from your Mac to `/var/lib/vz/template/iso/` on a PVE node, SSHive's SFTP pane handles it. Refresh the PVE web UI, the ISO is available for new VMs. Same for container templates in `/var/lib/vz/template/cache/`.

Frequently asked questions

Can SSHive replace the Proxmox web UI?+

No, the PVE web UI is the cleanest way to create/configure VMs. SSHive complements it: SSH for the host OS, VNC console for guest sessions, SFTP for file uploads. Use the web UI for VM lifecycle management, SSHive for everything else.

How do I securely access PVE web UI from outside my LAN?+

Don't expose 8006 on your router. Instead, use SSHive's tunnel feature: in the PVE node profile, add Local forward 8006 → localhost:8006. Connect via SSH, then open `https://localhost:8006` in Safari/Chrome. The web UI traffic is now tunneled through SSH.

Related SSHive features

SSH Terminal

GPU-accelerated terminal

VNC Viewer

Built-in VNC viewer

SFTP File Manager

Drag & drop file manager

SSH Tunnels

Local, remote & SOCKS5 proxy

Broadcast Mode

Multi-server command execution

Step-by-step guides

How to set up an SSH tunnel on a Mac

A complete guide to local, remote, and SOCKS5 SSH tunnels on macOS, both command-line and visually in SSHive.

How to VNC from a Mac to a Linux desktop

Built-in VNC viewer, full RFB protocol support, works with TightVNC/RealVNC/x11vnc/noVNC, and no separate WebSocket relay needed.

Run a command on multiple SSH servers from Mac

Broadcast keystrokes to every active SSH session at once, fleet-wide ops in seconds, no Ansible playbook required.

Common use cases

Manage your home server from your Mac

One app for everything in your home lab, SSH, SFTP, VNC, and secure tunnels for Plex, Home Assistant, Nextcloud, and more.

Kubernetes ops from your Mac

SSH to nodes, run kubectl from a unified terminal, tunnel cluster services, and broadcast across nodes, all in SSHive.

Try SSHive Free for macOS

Get the all-in-one SSH, SFTP, RDP and VNC client for Mac. Free download, no signup required.

Download SSHive Free How SSHive Compares