Troubleshooting

Login errors appear under the login form. Once logged in, errors from Proxmox VE and from the launchers appear in a notification at the bottom right of the main window, with the message as Proxmox VE returned it.

Login fails

• No reachable hosts found: none of the cluster’s Hosts answered within the timeout. Check the address and port (8006 by default) from the client, and the firewall between the two.
• Authentication failure: username without realm (alice instead of alice@pve), wrong password, or an OTP code missing or expired for an account with two-factor authentication.
• Certificate errors with the self-signed certificate of Proxmox VE: turn on Skip TLS certificate validation in the cluster, or install a trusted certificate on the nodes.

A VM or container is missing

cv4pve-vdi shows only guests there is something to do with; see Which guests appear. Check, in order:

1. Filters: the Status filter starts with Running only. Click × next to Filters.
2. Permissions: the account needs VM.Audit to see the guest at all, then VM.Console or VM.PowerMgmt; see Permissions.
3. Refresh (F5): the list is not refreshed by itself unless auto-refresh is on.

The Connect menu has only “Services…”

The guest offers no console: it is stopped, the account lacks VM.Console, or SPICE and VNC are off in Settings → Launchers. For SPICE the VM’s display must be SPICE; see SPICE and VNC.

SPICE or VNC does not open

• Warning remote-viewer is not configured: set the viewer path in Settings → Launchers; see Install remote-viewer.
• The viewer opens and closes, or cannot connect with SPICE: port 3128 of the SPICE proxy is not reachable from the client, or the proxy name does not resolve there. Set SPICE proxy in the cluster; see How it connects. VNC needs only the API port, so trying VNC tells a network problem from a VM problem.
• An error from Proxmox VE: its message says what was refused, e.g. a missing privilege.

A service does not start

• Could not resolve IP address for this VM: the guest agent is not installed or not running, the account lacks VM.GuestAgent.Audit, or the guest is a container. Set IP / hostname override in the service; see IP address.
• An error naming the executable: the program is not installed or not in the PATH. Set its full path in Settings → Launchers.
• The program starts but cannot connect: the guest’s port must be reachable from the client, and the service’s port must match the one the guest listens on.
• mstsc asks for the password: the service’s credentials are None, or the username or password is empty; see Single sign-on for RDP.

The agent badge stays grey

• Ping guest agent is off in Settings → Appearance: the badge only says the agent is enabled in the VM options.
• It is on and the badge is red: the agent does not answer; see Guest setup.

Start or Shutdown are missing

They are off by default: turn on Show Start button and Show Shutdown button in Settings → Appearance. They appear only on guests where the account has VM.PowerMgmt.