Search Results

Agent error code #200152 means the Palo Alto Networks firewall turned a User-ID update away because its management plane was occupied, not because anything about the request was wrong. A commit or push in progress is the usual reason. Knocknoc retries these au...

Agent error code #200153 means Knocknoc sent an IP-tag registration through Panorama for a specific firewall serial number, and Panorama could not reach that firewall to pass the request on. This is the User-ID equivalent of #200000, which covers the same prob...

Agent error code #200154 means the Palo Alto Networks firewall rejected the timeout Knocknoc set on the IP-tag mapping. Knocknoc registers each tag with a timeout matching the remaining session length, so the firewall expires the mapping by itself if the agent...

Agent error code #200155 means the Palo Alto Networks firewall does not have the virtual system that the knoc names, so it rejected the IP-tag registration. A firewall in single-vsys mode has one virtual system called vsys1. A firewall in multi-vsys mode has ...

Agent error code #200156 means the Palo Alto Networks firewall or Panorama rejected the API key Knocknoc presented when registering an IP-tag mapping. The credential was refused, so nothing about the request itself was evaluated. This covers the User-ID path s...

Agent error code #200157 means the API key Knocknoc presented is valid, but the administrator it belongs to is not permitted to submit User-ID updates. The firewall authenticated the request and then refused the operation. Registering an IP-tag mapping through...

Agent error code #200158 means the Palo Alto Networks firewall refused a User-ID registration because it is already holding as many registered IP addresses as its model allows. This is a capacity limit, not a busy device. Knocknoc does not retry it, because th...

Agent error code #200200 means the Knocknoc agent could not find out which firewall in an HA pair is active, so it had nowhere to send the grant. It applies only to a knoc configured with an HA peer and talking to firewalls directly. Where the knoc goes throug...

Agent error code #200201 means both firewalls in the HA pair answered the Knocknoc agent and neither reported itself active, so there was nowhere to apply the grant. This is the opposite situation from #200200. The checks worked. What they found is the problem...

Agent error code #299000 is the fallback the agent reports when a backend operation failed without supplying a specific reason. It carries no detail of its own, so the useful information is in the agent log rather than in this message. Every backend has its ow...

Agent error code #299001 indicates that the agent could not decrypt a stored secret (such as an API token or password) before using it to authenticate to a backend. Credentials are held encrypted and decrypted only at the moment they are needed; this error mea...

Agent error code #CFL002 indicates that Cloudflare returned HTTP 403. The API token is valid and does not carry the permission the operation needs. This is distinct from #CFL001, where the token itself was rejected. Common causes include: The token lacks the A...

Agent error code #CFL051 indicates that Cloudflare accepted the bulk operation and then reported it as failed. The request was well-formed enough to be queued, and the work itself did not complete. Common causes include: The list reached its maximum number of ...

Agent error code #CFL052 indicates that Cloudflare accepted the list update but had not finished applying it within the time Knocknoc waits. Cloudflare applies list updates in the background rather than as part of the request, so Knocknoc waits for it to repor...

Agent error code #202120 indicates that the ADOM configured on the knoc does not exist on FortiManager, or the administrator the agent authenticates as cannot see it. Common causes include: A typo in the ADOM field of the Knocknoc backend configuration. ADOM n...

Agent error code #202121 indicates that the target device is not present in the ADOM the knoc is configured to use. FortiManager found the ADOM and does not have that device in it. Common causes include: The device name on the knoc does not match its name in F...

Agent error code #202122 indicates that the address group named on the knoc does not exist on the target FortiGate. Common causes include: A typo in the address group name. Names are case-sensitive The group exists on a different FortiGate from the one targete...

Agent error code #202123 indicates that the FortiOS running on the target device does not provide the monitor endpoint the agent needs. The device answered, and the API surface Knocknoc relies on is not present in that version. Common causes include: The Forti...