PBS: Token can list datastores but not backup snapshots

[bretthabel]

Hi,

Fantastic work with 'Pulse', a great tool. Set it up earlier today using a LXC on my PVE, added the details for the PBS to the .env file and it seems to have an issue in that it won't list the details for 'snapshots'. Is this expected?

Diagnostics reports the following:

_[WARNING] PBS Permissions: PBS "pbs": Token can list datastores but not backup snapshots. This may affect backup overview functionality.

[WARNING] PBS Data: PBS is configured but no backups were found. Verify that backups exist in your PBS datastores and that the API token has permission to read them._

Any help most appreciated!

[rcourtman]

Hi @bretthabel!

I've implemented PVE backup support that should resolve this issue. The problem was that Pulse only supported PBS backups, but many users (like yourself) have PVE-only setups without PBS or use local PVE backups alongside PBS.

Test the Fix

I've made it easy to test this feature before the next official release:

1. Update your install script (this gets the latest testing functionality):

   sudo /opt/pulse-proxmox/scripts/install-pulse.sh

   Select Y when it asks to update the installer script.

2. Select the test branch: From the menu, choose "Test a feature branch" and select feature/pve-backups-support.

What This Fixes

• ✅ No more PBS token warnings for PVE-only setups
• ✅ Shows your PVE backups in the backups tab (vzdump tasks, storage backups)
• ✅ Displays VM/CT snapshots with a modal view
• ✅ Combined view of both PBS and PVE backups if you have both

Return to Stable

Once you've tested it, you can easily return to the stable version:

sudo /opt/pulse-proxmox/scripts/install-pulse.sh

Choose "Update Pulse to the latest version" to go back to the stable release.

Let me know how the testing goes! 🚀

[rcourtman]

Closed by accident, reopening

[SovetickaLAB]

I've tried this fix, but really difficult way. I have it deployed in docker, so I've manually downloaded all of the changed files in the commit and replaced them, then restarted the container.

From what I can see, nothing really changed. I have both PVE and PBS added with Admin rights. Diagnostics reports "[WARNING] PBS Data: PBS is configured but no backups were found. Verify that backups exist in your PBS datastores and that the API token has permission to read them. "

I will try to install it via Automated install from community scripts.

[SovetickaLAB]

Nvm, cannot install it due to the same issue as in #84

[SovetickaLAB]

Okay, nvm again, got it working.. somehow... but when I try to update Pulse with the script from

/opt/pulse-proxmox/scripts/install-pulse.sh

Update the script and then choose the test branch, it won't actually update Pulse to the test branch.
root@pulse:/opt/pulse-proxmox# cat package.json { "name": "pulse", "version": "3.11.1",

[bretthabel]

Thanks for the prompt reply on this! In attempting to run the script (in the Proxmox LXC shell, as well as via SSH), it returns the following error:

Do you want to proceed with the installation/update? [Y/n]: y
[INFO] Proceeding...
[INFO] Checking Pulse installation at /opt/pulse-proxmox...
[ERROR] Directory /opt/pulse-proxmox exists but does not appear to be a valid Pulse git repository.
[ERROR] Please remove this directory manually (/opt/pulse-proxmox) or choose a different installation path and re-run the script.
[ERROR] Exiting due to error.

May be related to #84 as noted above? Thanks again.

[bretthabel]

Fixed! (3.12.3)