PROX104 - Proxmox Node Or VM Not Found

Agent error code #PROX104 indicates that, for a per-VM (qemu) scoped Knoc, Proxmox VE could not find the node or VM the agent was directed to.

This applies only to per-VM scope. For cluster-scoped Knocs the agent does not target a node or VM, and a missing ipset returns #PROX100 instead.

Common causes include:

• The Proxmox node name in the ACL has a typo (names are case-sensitive)
• The VM ID does not exist on the configured node
• The VM was migrated to a different node and the ACL still points at the old one
• The VM was deleted after the Knoc was configured

Steps to Resolve

Verify Node and VM ID

1. In the Knocknoc admin interface, edit the affected Knoc's ACL
2. Confirm the Scope is per-VM
3. In the Proxmox web UI, find the VM and note the node it currently runs on and its VM ID
4. Set the ACL's Proxmox node and VM ID to match, then save

Check for Migration

If the VM has been migrated, update the ACL's node to the VM's current node. If you use HA and the VM moves between nodes, consider whether a cluster-scoped ipset is a better fit.

For more details, see the Proxmox setup guide.

Still Having Issues?

We can help you out, contact us at [email protected].