Search Results

Agent error code #PROX103 indicates that the agent tried to remove an IP address from the configured Proxmox VE ipset and Proxmox rejected the operation. The agent only adds and removes ipset entries. If the ipset is missing the agent returns #PROX100 instead....

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 ips...

Agent error code #PROX400 indicates that the agent received a response from Proxmox VE that it could not parse as the expected ipset data. The request reached Proxmox, but the body was not in the form the agent expected. Common causes include: The backend URL...

Agent error code #F5000 indicates that the Knocknoc agent could not establish a network connection to the F5 BIG-IP management endpoint at all. The connection failed before any authentication could take place. This is distinct from authentication (#F5001) and ...

Agent error code #F5001 indicates that the F5 BIG-IP rejected the username and password supplied by the Knocknoc agent. The device returned HTTP 401 Unauthorized when the agent tried to obtain an authentication token. This is distinct from authorization failur...

Agent error code #F5002 indicates that the F5 BIG-IP accepted the credentials but the user's role does not have permission to perform the requested operation on the data-group. The device returned HTTP 403 Forbidden. This is distinct from authentication failur...

Agent error code #F5003 indicates that the TLS handshake with the F5 BIG-IP management endpoint failed. The agent reached the device but could not verify its certificate. Common causes include: The BIG-IP presents its default self-signed management certificate...

Agent error code #F5004 indicates that a request to the F5 BIG-IP management endpoint did not complete within the allowed time. The device did not respond, or responded too slowly. Common causes include: The BIG-IP management plane is under heavy load or unres...

Agent error code #F5005 indicates that the login request to /mgmt/shared/authn/login did not return a usable token, even though the agent reached the device. The response was missing the token, or the login endpoint returned an unexpected result that was not ...

Agent error code #F5050 indicates that the agent authenticated successfully but the GET request for the configured internal data-group failed for a reason other than the data-group simply not existing (which is reported as #F5051). Common causes include: A tra...

Agent error code #F5051 indicates that the internal data-group named in the Knocknoc backend does not exist in the configured partition on the F5 BIG-IP. The device returned HTTP 404 Not Found. Knocknoc does not create the data-group; an administrator must cre...

Agent error code #F5052 indicates that the configured data-group exists, but it is not an Address (type ip) data-group. Knocknoc stores granted IPs as address records, so the target must be an address data-group. Common causes include: The data-group was crea...

Agent error code #F5053 indicates that the PATCH request to update the data-group's records failed. The agent could read the data-group but could not write the new record set. Common causes include: The service account's role can read but not modify the data-g...

Agent error code #F5400 indicates that the F5 BIG-IP returned a response the agent could not interpret: a body that did not parse as the expected iControl REST JSON, or an unexpected HTTP status that did not map to a more specific code. Common causes include: ...

Agent error code #OPN006 is the fallback code for OPNsense API errors that don't match a more specific classification. The agent reached the firewall and the call completed, but the response indicated a transport-level or unclassified failure. This error is di...