Skip to main content

PROX100 - Proxmox Ipset Not Found

Agent error code #PROX100 indicates that the ipset configured in the Knocknoc ACL does not exist on the Proxmox VE cluster (or on the configured VM, for per-VM scope). The cluster returned HTTP 404 when the agent looked it up.

This error is distinct from authorization failures (#PROX001), which occur when the API token is denied even for ipsets that exist. Error #PROX100 means the ipset name itself was not found.

Common causes include:

  • The ipset has not been created on Proxmox yet
  • The ipset name in the Knocknoc ACL has a typo (names are case-sensitive)
  • The scope is wrong: the ipset exists at cluster level but the Knoc points at a VM (or vice versa)
  • The Knoc points at the wrong Proxmox node or VM ID so the agent is looking on a host or VM that doesn't have the ipset
  • The ipset was renamed or deleted on Proxmox after the Knoc was configured

Steps to Resolve

Verify the Ipset Exists on Proxmox

  1. Log into the Proxmox web UI
  2. For cluster-scoped Knocs, navigate to Datacenter > Firewall > IPSet
  3. For per-VM Knocs, navigate to the target VM > Firewall > IPSet
  4. Confirm an entry exists with the exact name configured in the Knocknoc ACL
  5. Names are case-sensitive (e.g. knocknoc_allowed is different from Knocknoc_Allowed)
  6. If the ipset is missing, create it and leave the contents empty. The agent will populate it on the next grant

For more details, see the Proxmox setup guide.

Verify Scope, Node and VM ID

  1. In the Knocknoc admin interface, edit the affected Knoc's ACL
  2. Confirm the Scope (cluster or per-VM) matches where the ipset was created
  3. For per-VM scope, confirm Proxmox node and VM ID point at the VM that holds the ipset
  4. Save the ACL

Add a Rule That References the Ipset

The agent only manages ipset contents. It does not create rules. Once the ipset exists, add a firewall rule under Firewall > Rules that references it (use the source / destination dropdown to pick +<ipset name>).

Still Having Issues?

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

Back to top