rcourtman b0b790cf55 Fix PVE token re-registration after agent reinstall ...

When the agent is reinstalled on a Proxmox host, it rotates the PVE API
token in Proxmox but the Pulse server's /api/setup-script-url endpoint
requires settings:write scope — agent tokens only have agent:report — so
the 401 aborted the update, leaving Pulse with a stale token and a
disconnected PVE node.

Three-part fix:
- server: accept agent API tokens on /api/auto-register for updating
  existing nodes (new nodes still require setup-token auth)
- agent: fall through instead of aborting when setup token fetch returns
  4xx; send X-API-Token header so the server can authenticate via the
  agent token instead
- update: allow HTTP auto-update URLs for RFC 1918 private network
  addresses (LAN installs without HTTPS no longer block auto-update)

2026-04-18 21:44:42 +01:00

..

coverage_test.go

feat: Pulse v6 release

2026-03-18 16:06:30 +00:00

export_test.go

feat: Pulse v6 release

2026-03-18 16:06:30 +00:00

restart_unix.go

Improve internal package test coverage

2025-12-29 17:25:21 +00:00

restart_windows.go

Fix Windows agent self-update restart failure

2025-11-30 12:02:43 +00:00

update_hostagent_integration_test.go

feat: Pulse v6 release

2026-03-18 16:06:30 +00:00

update_http_test.go

feat: Pulse v6 release

2026-03-18 16:06:30 +00:00

update_test.go

feat: Pulse v6 release

2026-03-18 16:06:30 +00:00

update.go

Fix PVE token re-registration after agent reinstall

2026-04-18 21:44:42 +01:00