Search Results

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

Knocknoc normally grants access to the single IP a user authenticates from. Agentic Access and Companions extend that for two cases: granting time-limited access to an automated agent, and keeping access for a user's other companions, such as a second device o...

Knocknoc integrates with Cisco Meraki to dynamically control which source IPs are allowed through Meraki MX firewall policy. The integration uses the Meraki Dashboard API to maintain a single Policy Object Group per Knoc. The orchestration is performed by a Kn...

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