Troubleshooting

Site shows Offline

Start by checking the Agent services on the affected Proxmox node.

sudo systemctl status hsve-agent --no-pager
sudo systemctl status hsve-agent-console --no-pager
sudo systemctl status hsve-agent-management --no-pager
sudo systemctl status hsve-agent-deployment --no-pager

sudo journalctl -u hsve-agent -n 100 --no-pager

• Confirm the host can resolve and reach portal.hsve.co.uk over HTTPS.
• Check that /etc/hsve-agent.env exists and has not been manually damaged.
• If the Agent was revoked, create a fresh re-enrolment rather than trying to reuse the old cloud credential.

Site is online but inventory is empty

• Give the Agent a short period to complete its first inventory sync.
• Refresh Portal after the heartbeat becomes current.
• Check hsve-agent and hsve-agent-management logs for local Proxmox API errors.
• Confirm local hostname/DNS and Proxmox TLS certificate validation are working.

Virtual KVM will not connect

• Confirm the guest is running.
• Confirm hsve-agent-console is active on the Proxmox node hosting the guest.
• Reconnect the console to force a fresh short-lived session.
• Do not open Proxmox TCP 8006 publicly as a workaround; fix the Agent/relay path instead.

sudo journalctl -u hsve-agent-console -n 100 --no-pager

Windows Remote Desktop will not connect

• Confirm the Windows edition can host RDP.
• Enable Remote Desktop inside Windows.
• Confirm the Remote Desktop service is running and listening on TCP 3389 inside the VM.
• Install and enable QEMU Guest Agent so Portal can discover guest networking.
• Verify the Proxmox host can reach the Windows VM on TCP 3389 over the internal network.

Marketplace deployment is blocked

• Confirm the product is Purchased and the release says Ready to deploy.
• Confirm the target node has an online/current Agent.
• If Portal says Agent update required, update the Agent before retrying.
• Choose active VM-capable storage and an active bridge.
• Use a Proxmox-safe VM name such as Windows-11-Design rather than a name containing spaces.
• Leave VM ID on Auto if a manually selected ID conflicts with existing inventory.

Agent installer reports a Proxmox TLS error

HSVE deliberately refuses to disable Proxmox certificate verification. Ensure the Proxmox node hostname resolves locally and that the certificate chains to the system trust store or the Proxmox cluster CA at /etc/pve/pve-root-ca.pem, then rerun the installer.

When to contact HSVE

If an Agent is repeatedly failing enrolment, a Portal action is consistently rejected despite correct role/health, or a deployment fails after the job has started, capture the relevant Site name, node name, VM/CT ID and recent Agent service logs before contacting HSVE support. Do not send /etc/hsve-agent.env or API token secrets.