Search Results

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

Agent error code #MERA000 indicates the agent could not establish a connection to the Meraki Dashboard API. The request never reached a successful response. Common causes include: The agent host has no outbound HTTPS path to api.meraki.com (or your regional h...

Agent error code #MERA001 indicates the Meraki Dashboard rejected the API key in the agent's Authorization: Bearer <key> header (HTTP 401). This is distinct from authorization failures (#MERA002), where the key is valid but lacks access to the configured orga...

Agent error code #MERA002 indicates the API key authenticated successfully but is not authorized to access the configured organization (HTTP 403), or the organization could not be accessed with this key. Common causes include: The administrator behind the API ...

Agent error code #MERA003 indicates a TLS/SSL certificate error while connecting to the Meraki Dashboard. Common causes include: A TLS-intercepting proxy on the agent host presents a certificate the agent does not trust The agent host's trusted CA store is out...

Agent error code #MERA004 indicates a request to the Meraki Dashboard did not complete within the timeout. Common causes include: Intermittent network problems between the agent host and the Dashboard A slow or saturated proxy on the agent host Steps to Resolv...

Agent error code #MERA005 indicates the Meraki Dashboard API rate-limited the agent (HTTP 429). The Dashboard caps calls at 10 per second per organization. The agent automatically backs off and retries (honoring the Retry-After header) before surfacing this e...

Agent error code #MERA050 indicates the agent could not read the configured Meraki organization. Common causes include: The Organization ID is incorrect The API key lacks access to the organization (see #MERA002) Steps to Resolve In the Meraki Dashboard, confi...

Agent error code #MERA100 indicates the agent could not read the configured policy object group. Common causes include: A transient Dashboard error or rate limit The Policy Object Group ID is incorrect (see #MERA102) Steps to Resolve Verify the Policy Object G...