Search Results

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

Agent error code #PROX101 indicates that the agent reached Proxmox VE and the ipset lookup did not fail with a not-found or permission error, but the response could not be used to read the current ipset contents. This is distinct from #PROX100 (the ipset does ...

Agent error code #PROX102 indicates that the agent tried to add an IP address to the configured Proxmox VE ipset and Proxmox rejected the operation. The agent only adds and removes ipset entries. It does not create the ipset itself. If the ipset is missing the...

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 #KEMP000 indicates that Knocknoc could not reach the Kemp LoadMaster API. The connection could not be established. This error is distinct from authentication failures (#KEMP001), authorization failures (#KEMP002), TLS errors (#KEMP003), timeou...

Agent error code #KEMP001 indicates that Knocknoc reached the Kemp LoadMaster but the username or password was rejected. The API returned HTTP 401 Unauthorized. This is distinct from an authorization failure (#KEMP002), where the credentials are valid but the ...

Agent error code #KEMP002 indicates that the credentials authenticated successfully but the user lacks the permissions required to read or modify the global ACL. The API returned HTTP 403 Forbidden. Common causes include: The user account does not have All Per...

Agent error code #KEMP003 indicates that Knocknoc could not establish a trusted TLS connection to the Kemp LoadMaster. The LoadMaster's certificate could not be verified against Knocknoc host's trust store. LoadMasters often ship with a self-signed management ...

Agent error code #KEMP004 indicates that Knocknoc opened or attempted a connection to the Kemp LoadMaster but the request did not complete within the allowed time. A timeout differs from a refused connection (#KEMP000). The host is reachable enough to start a ...

Agent error code #KEMP005 indicates that Knocknoc reached the LoadMaster but the API endpoint was not found. The API returned HTTP 404 Not Found, which usually means the API Interface is not enabled. Knocknoc manages the global allowlist through the LoadMaster...

Agent error code #KEMP100 indicates that Knocknoc could not read the global ACL allowlist it is supposed to manage. A failure here usually points at a permissions or API availability problem rather than a missing list. If the allowlist simply has no entries ye...

Agent error code #KEMP101 indicates that Knocknoc could read the global ACL but the call to add an address to the allowlist failed. An add failure usually points at a permissions boundary on the write path or a transient LoadMaster error. Common causes include...

Agent error code #KEMP102 indicates that Knocknoc could read the global ACL but the call to remove an address from the allowlist failed. This typically happens when a grant expires and Knocknoc tries to revoke access. The address remaining in the allowlist aft...

Agent error code #KEMP400 indicates that Knocknoc reached the Kemp LoadMaster and received a response, but the response did not match the expected shape. The most common case is a non-success status carrying an error message in the body. Less commonly, a succe...

Configure 1Kosmos as a SAML identity provider (IdP) for Knocknoc. Once connected, your users authenticate against 1Kosmos — including its biometric and passwordless factors — and Knocknoc maps their group membership to access entitlements. This example assumes...