Frequently asked questions

Short answers, each linked to the part of the documentation that explains it in full.

About PMClient

What does PMClient cost?

It is free for non-commercial use. Commercial use includes a 60-day trial, after which a commercial licence is needed.

When can I download it?

Soon. PMClient is with testers now, and downloads open with the first public release.

Which languages is PMClient available in?

English. Other languages are planned.

Installing and requirements

Which platforms does PMClient run on?

Windows, macOS and Linux, natively on both x86_64 and ARM64 on each. On macOS it needs macOS 14 or newer, and the osx-arm64 and osx-x64 builds are not interchangeable. See Getting started.

Which Proxmox VE versions does it work with?

Proxmox VE 8.x or 9.x, tested mostly on 9.2. Seamless clipboard in VM consoles additionally needs PVE 8.1 or later.

Does it work with Proxmox VE 7?

It has not been tested on Proxmox VE 7. Much of it may work, but PVE 7 is not supported.

On Linux, why does dpkg -i complain about the package?

dpkg -i does not resolve dependencies. Install with sudo apt install ./wickasoft-pmclient_<version>_amd64.deb (or the arm64 package), keeping the ./ so apt treats the file as a local package and pulls in what it needs. See Getting started.

Connecting and certificates

How do I log in with an API token?

Enter user@realm!tokenid as the user and the token secret as the password. Tokens are privilege-separated by default in Proxmox VE, so grant the ACL to the token itself or disable privilege separation on it. See Connecting and Permissions.

Can I sign in through single sign-on?

Yes, through any realm on the cluster whose type is openid; pick it and sign-in happens in a browser. PMClient fronts the cluster's own OpenID flow with the same redirect the web UI uses, so nothing changes in your provider's app registration. See Connecting.

Can I reach a cluster that is only accessible through a jump host or proxy?

Yes. Put an SSH jump host (user@jumphost) or a SOCKS5 proxy (socks5://host:port) in the Via box. A routed connection never falls back to a direct one; if the route cannot be used, PMClient says why. See Through a jump host or proxy.

How should I check the certificate fingerprint PMClient shows on first connection?

Check it out of band: on the node, over a console or SSH, run openssl x509 -in /etc/pve/local/pve-ssl.pem -noout -fingerprint -sha256 and compare the output directly. Comparing in the Proxmox web interface proves nothing, because the browser is shown the same certificate. You are asked once per cluster, not once per node. See The certificate question.

The certificate changed and PMClient refuses to connect. How do I accept the new one?

There is no override: a certificate that stops matching what you approved is refused outright, and there is deliberately no "ignore" button. If the change was legitimate, first check the new fingerprint on the node itself, over SSH or at its console. Then, signed out, choose Forget saved certificate on the connection form. It removes the saved pin, the certificates you accepted and the cluster's certificate authority for that host from every profile that connects to it, and keeps the profiles, users and passwords. The next connection asks you to confirm the fingerprint, as on first contact. See The certificate question.

Does PMClient store my password?

Never as cleartext. The operating system's secret store (DPAPI on Windows, the login Keychain on macOS, Secret Service on Linux) holds the key, and only an encrypted token sits beside the profile; where no store is available, nothing is kept and PMClient asks again next launch. See Where it writes.

Consoles

Why doesn't copy and paste work in a VM console?

It needs two things: clipboard=vnc on the VM's display (PVE 8.1 or later) and the clipboard agent running inside the guest. The console's hint bar reports which one is missing, and offers a one-click Enable clipboard if your account may change VM hardware. See Copy & paste.

How do I copy and paste in a container console or node shell?

Copy is Ctrl+Shift+C (Cmd+C on a Mac); plain Ctrl+C is left alone so it keeps working as interrupt. Right-click pastes. See Text consoles.

Why do full-screen programs look wrong in a container console?

A container console starts with TERM=linux. Run export TERM=xterm-256color, or plain xterm on a guest whose terminfo lacks that entry. See Text consoles.

Cluster operations

Can I live-migrate a VM without shared storage?

Yes. A running VM with disks on ZFS, LVM or a plain directory can move: Proxmox VE mirrors the disks to the target while the guest keeps running, and the Migrate to menu shows how much will be copied. See Migration.

Why is a migration target grayed out, or the guest marked Blocked?

PMClient lists nodes that cannot take the guest as disabled, with the reason, and shows Blocked with the reason when the guest cannot move at all, before anything starts. The migration matrix in the docs lists the common causes, such as local snapshots without replication, a local ISO in the CD drive, or unmapped passthrough hardware. See Migration.

What account does the rolling cluster update need?

A root@pam login; no other account can run an update. The run does not set or clear Ceph's noout, so handle that yourself around the run. See Updating the whole cluster.

What happens if a step fails during a rolling update?

The run pauses and waits for you; it never moves on by itself. On the Updates page you can run the step again where that can help, skip that node, or stop. See Updating the whole cluster.

Troubleshooting

PMClient won't start, or something looks broken. What should I run?

Run it from a terminal with --self-test. It opens the real windows, checks assets, theming and the password store, prints a line per check and exits with a pass/fail code. See Troubleshooting.

PMClient crashed. What should I send?

Every crash is appended to crash.log in the settings folder, with the version, OS and architecture. That file, plus what you were doing at the time, is the fastest route to a fix. See Where it writes.

Where do I report a bug?

For now, report it to the contact you received your build from, with crash.log or a screenshot if you have one. A support portal for questions and bug reports, with attachments, is being set up.