Troubleshooting

This page gathers the most common problems and how to solve them.

”proxmox-backup-client binary not found”

A banner appears at the top of the interface when proxmox-backup-client is not present on the host. Cloud-PBS TUI still opens, but no real backup or restore is possible.

Fix: install proxmox-backup-client. The simplest way is to run the install script again, which takes care of it. See Installation.

A backup’s contents do not show up

During a selective restore, browsing a backup’s contents relies on a FUSE mount. If FUSE is missing, the tool cannot show the contents and says so with a message inviting you to install the fuse3 package.

Fix: install FUSE.

• Debian / Ubuntu: apt install fuse3
• RHEL / CentOS / Rocky: dnf install fuse fuse3
• openSUSE: zypper install fuse3

Then start the restore again.

”Insufficient permissions” when browsing backups

The Backups screen reports that the token cannot read the datastore. This happens with a token holding only the Datastore.Backup privilege: it can write backups, but not list or restore them.

Fix: grant the token the Datastore.Read (or Datastore.Audit) privilege on the datastore, on the PBS server or from the Cloud-PBS dashboard. See Connecting to the PBS server.

The connection test fails

If the Test action of the Target screen fails, check, in order:

• the server URL and port (PBS listens on port 8007 by default);
• the certificate fingerprint if the server uses a self-signed certificate;
• the token Auth ID and Secret: since the secret is shown only when the token is created, a typo means you have to create a new token;
• network connectivity between the host and the server.

A scheduled backup does not run

Scheduled backups are triggered by systemd. If an expected backup did not happen:

• check that the schedule was actually applied from the Schedule screen;
• at the user level, timers only run while the user’s systemd session is active; enabling lingering (loginctl enable-linger) lets them run even with no open session;
• inspect the timer state with systemctl list-timers (add --user for a user-level installation).

The restore does not bring back file ownership

The restore preserves file modes and modification times, as well as symbolic links, but not ownership (owner and group) when the tool runs without privileges.

Fix: run Cloud-PBS TUI as root if you need the original uid/gid back.

Going further

If a problem persists, the Cloud-PBS team can help: see the Support page or contact us.