Frequently Asked

Last updated: 21 April 2026

Which Proxmox versions are supported?

Proxmox VE 7.x and 8.x are the tested targets. The app uses standard REST endpoints (/api2/json/...) that have been stable for years. If something breaks on a specific minor release, file it on support.

Does the app work with a cluster or only a single node?

Both. The app queries /cluster/resources which returns all nodes, VMs, containers, and storages. Single-node installs look the same as a one-node cluster.

Do I need a backend, a relay, or an account?

For default direct-API usage: no. Your iPad talks straight to your Proxmox server — no account with us, no cloud relay. If you want the optional cloud features (push, remote access, cross-cluster view), you install a small self-hosted daemon on a machine in your network and take out a Cloud subscription. The daemon talks to our EU-hosted Supabase backend, never exposes your Proxmox credentials, and you can filter its outgoing traffic to one endpoint in your firewall.

What are cloud features, and how do they work?

Cloud features are opt-in add-ons: push notifications (node offline, backup failed, VM down), remote access when you're outside your local network, and a cross-cluster aggregated dashboard across multiple Proxmox hosts.

They require proxmoxvue-agent, a small self-hosted daemon. You can run it on the Proxmox host itself, on any Linux machine in the same network (a Raspberry Pi 4/5 with 64-bit OS works great), or as a Docker container — whichever fits your setup. Install it once, and the app picks up the cloud path automatically for subscribed users. Your iPad keeps using direct API for everything else.

Can I run the agent on a separate machine, a Raspberry Pi, or in Docker?

Yes — all three. The agent is a single Go binary with three deployment options:

  • On your Proxmox host — simplest path, fewest moving parts. The default install uses https://127.0.0.1:8006 for the Proxmox API.
  • On a separate Linux machine in your network — keeps your hypervisor pristine. We ship amd64 and arm64 binaries, so a Raspberry Pi 4 or 5 running 64-bit Raspberry Pi OS or Ubuntu works out of the box. Older Pi 3 / 32-bit ARM (armv7) is not supported by the prebuilt binary. The agent reaches your Proxmox host over your LAN on port 8006.
  • As a Docker container — same binary, configured via environment variables. See DOCKER.md for the env-var reference and a docker-compose.yml example.

One agent enrollment maps to one Proxmox host — for multiple hosts, run multiple instances (separate machines, or one machine with multiple containers).

Does the daemon need firewall changes?

No inbound firewall rules. The daemon only makes outbound connections — to one endpoint (our EU-hosted Supabase backend).

You can optionally restrict its egress in your own firewall to just that one host: full control over where the daemon communicates. Since connections are daemon-initiated, no port needs to be opened on your router.

Where do I get the agent, and how do I install it?

proxmoxvue-agent is open source. The repository — including build instructions, a sample systemd unit, and config templates — lives on GitHub: github.com/TheLion/proxmoxvue-agent.

You only need it if you want the cloud features (push, remote access, cross-cluster view). For default direct-API use of the app, the agent is not required.

How do I log in?

Three ways, pick what matches your setup:

Username + password + realm — same as the Proxmox web UI. Use PAM, PVE, LDAP, or AD.

OIDC — if your realm is Authentik, Keycloak, or any other OpenID Connect provider, the app opens your browser for the login and catches the callback. You need to allow proxmoxvue-auth://callback as a redirect URI in your provider.

API Token — classic scoped tokens. Toggle "Use API-token instead" in the add-host screen.

My Proxmox uses a self-signed certificate. Will it work?

Yes. Flip the "Accept self-signed TLS" toggle when adding the host. The app disables certificate validation for that host only — other hosts are still validated.

Where are my credentials stored?

In the iOS Keychain, which is:

— encrypted at rest by the OS,
— only accessible when the device is unlocked,
— never synced to iCloud,
— scoped to this app only.

OIDC session tickets are held in memory only — never persisted. A fresh browser login is required if the ticket expires.

Why is the app iPad-first?

The iPhone market has several Proxmox apps. The iPad doesn't. We thought that was a gap worth filling: tab navigation across cluster/nodes/VMs/LXC/storage with drill-down detail views, long-press context menus, big tap targets, and a distinctive dark terminal-inspired aesthetic — a touch-native tool designed for the size, not a phone UI stretched to 11 inches. An iPhone companion is on the roadmap (push notifications, widgets, quick actions) but won't ship as a full management tool.

Will there be a Mac version?

No. The Proxmox web UI on a desktop is good enough; a Mac app would add too little to justify the build cost.

Is the source open?

The iPad app itself is closed source — we may reconsider later.

The cloud agent (proxmoxvue-agent) is open source: github.com/TheLion/proxmoxvue-agent. You run it yourself and can audit exactly what it sends.

How do I report a bug?

See the support page — we read everything.

← Back to ProxmoxVue