Search Results

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

Knocknoc 26.07.1 is one of our biggest releases to date. It reworks how you see and manage the people, devices and sessions accessing your network, improves multi-server high availability enablement that you can configure from the admin portal, ships two new i...

Agent error code #CFL100 indicates that the Knocknoc Cloudflare Lists backend has neither a List ID nor a List Name configured. The agent cannot tell which Cloudflare rule list to update, so the grant fails before any Cloudflare API call is made. This is a con...

Agent error code #CFL101 indicates that the Knocknoc backend is configured with a Cloudflare list name, and no rule list with that name exists in the configured Cloudflare account. The agent looks the name up to resolve it to a list ID, and that lookup returne...

Agent error code #CFL102 indicates that the Knocknoc backend tried to resolve the configured Cloudflare list name to a list ID, but Cloudflare returned an unexpected response. The list may well exist; the request to enumerate lists did not succeed. This differ...

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

Agent error code #MERA101 indicates the agent could not update the membership of the configured policy object group. Common causes include: A transient Dashboard error or rate limit The API key's administrator lacks write access to policy objects Steps to Reso...

Agent error code #MERA102 indicates the configured policy object group could not be found (HTTP 404). Common causes include: The Policy Object Group ID is incorrect The group was deleted in the Meraki Dashboard Steps to Resolve In the Meraki Dashboard, go to O...