rcourtman
0a7a9490d5
An existing collector can retain its legacy TLS bypass after the host trusts the Pulse certificate. Updating it with action-runner enrollment then incorrectly rejects normal system-root trust and enters recovery before creating the runner service. Keep collector/download settings separate from verified runner TLS. HTTPS runner configuration continues to use system roots, a configured CA or an exact certificate pin and never inherits the collector bypass. Activation, cancellation, revocation and service recovery retain their existing boundaries. Validation: the new executable regression fails against the previous installer and passes with the fix. It covers recovered insecure state, private configuration persistence and the real runner credential lifecycle binary over TLS. System roots, custom CA and exact pin succeed. Untrusted certificates and incorrect pins receive no credential-bearing request. The installer Action Runner suite, runner binary tests and hostagent Action Runner suite pass. Agent Doctor enrollment also passes in the current built app at 1440, 820 and 390 pixels wide, covering details disclosure, issue failure/pending/success, private command copying, one-time reveal, clearing and reload. Browser endpoints use synthetic fixtures. No native installed-host or published-release acceptance is claimed. The additional native workflow passes on Linux x64 and ARM64. Its macOS Intel and ARM64 jobs fail the unchanged Upstart retirement contract because the host `ln` rejects `-T`. The same failure occurs in [the earlier main run](https://github.com/rcourtman/Pulse/actions/runs/38899584939). This change does not touch that fixture or the exercised retirement functions.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Need help with a failure? Read the safe reporting guidance before sharing evidence. A second reproduction or diagnostics export is not required; keep the original evidence if another attempt could interrupt workloads or send duplicate notifications. GitHub reports and attachments are public: review them locally and keep credentials and private details out.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.