Updates

The Connector updates itself automatically, so deployed Connectors stay current without manual intervention.

How it works

• About 30 seconds after startup, and then every ten minutes, the Connector checks the release feed at releases.prod.firemon.cloud for a newer version.
• If a newer version is available, it's downloaded, verified, and installed automatically, and the Connector restarts on the new version.
• On the OVA appliance (systemd), the restart is staged so a failed or crash-looping update automatically rolls back to the previous binary. The Linux service install verifies updates the same way but can't roll one back; an update that keeps crashing leaves the service stopped.
• On macOS, Windows, and a standalone Linux binary, the running process is replaced and relaunched in place. If the new binary fails to launch, the previous one is restored automatically. A new version that launches and then crashes is not rolled back.

The Connector defers an update while it has work in flight (for up to 12 hours), so it won't abandon a job partway through.

Verification before installing

Every update goes through multiple checks before it's applied:

1. Signature verification. The release manifest is signed at release time, and the Connector verifies that signature with a public key embedded in the binary before it downloads anything.
2. Checksum verification. After downloading, the Connector verifies the file's checksum against the signed manifest.
3. Source validation. Downloads are only accepted from the release domain, releases.prod.firemon.cloud.
4. Re-verification at install. On Linux, the service checks the binary's hash once more immediately before installing it. On macOS and Windows, the extracted file's size and checksum are checked against the archive. Either way a truncated or corrupted download is discarded rather than installed.

An update that fails any of these checks is rejected, and the Connector keeps running its current version.

Disabling auto-update

If you need a Connector to stay on a fixed version, for example while validating a change in a controlled environment, set the environment variable FIREMON_AUTO_UPDATE=false before starting it. The Connector still checks for and logs available updates, but won't download or install them.

On the OVA appliance, set this in /etc/firemon-connector/env and restart the service.

We recommend leaving auto-update enabled for production deployments so Connectors always run a current, supported version.

Version format

Versions are shown as <semver>-<build-id> (e.g. 1.2.3-abc123def456). The build ID is included so that even patch-level rebuilds are distinguishable.

firemon-connector --version prints the running version and build, which is the quickest way to confirm an update landed.