Reddit POST you might want to Address - Pulse Monitoring Tool - Not as Free as the Reviews?

[kenrmayfield]

@rcourtman

Giving you a Heads Up................................

You might want to Address this Reddit POST:

Pulse Monitoring Tool - Not as Free as the Reviews?
https://www.reddit.com/r/Proxmox/comments/1sqo58g/pulse_monitoring_tool_not_as_free_as_the_reviews/

[FuturamaPhill]

I saw your comment responding to the now deleted post and I think you should review some of the more recent comments on it before it was deleted. It actually appears as if there is an issue in the installer script as I'm experiencing the same issue, i used the recommend LXC command and it installed the pre-release version 6 which appears to be limited to 1 device, yes its showing an expired pro plan but there appears to be no option to change that in the GUI and the documentation does not make it clear how to resolve this issue.

[kenrmayfield]

@FuturamaPhill

It just does not Adding Up because the Quick Start Recommended Commands Install PULSE based on the TAG: Latest or Release: (Version Number) listed within the Commands.

You can go back and Install the v5.1.28 however I have PULSE installed in a VM on Alpine OS with v5.1.28.

What is the Install Command did you use?

I did a Test for Installing PULSE in a LXC for the Latestest with the Quick Start Recommended Install Commands and v5.1.28 was Installed with Both Recommended Commands:

FROM THE INSTALL.MD PAGE:

curl -fsSL https://raw.githubusercontent.com/rcourtman/Pulse/release/5.1/install.sh | bash

FROM THE PUSLE MAIN PAGE:

curl -fsSL https://github.com/rcourtman/Pulse/releases/latest/download/install.sh | bash

[FuturamaPhill]

I logged a bug report for it #1435

I used latest and 5.1 curl and they both downloaded the pre-release version

[rcourtman]

Thanks for flagging this. I tracked it down and there were real bugs here. The recommended LXC installer path could incorrectly land on the v6 prerelease, and that prerelease could surface an incorrect self-hosted monitored-system limit / expired Pro state. I’ve fixed the installer issue and the self-hosted entitlement bug locally and I’m getting those changes out. I appreciate the heads up.