Search Results

Agent error code #299006 occurs when an agent is newer than its server, and the server sent a configuration in a format too old for the agent to convert. The agent reports the error but the server is out of date, so upgrading the agent will not fix it. Steps t...

Agent error code #299007 occurs when a knoc's predefined source is a network, such as 192.168.100.48/29, and the agent serving the knoc is too old to grant one. An older agent would grant only the network's first address while reporting the whole network grant...

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 on the knoc does not exist in the knoc's partition on the F5 BIG-IP. The device returned HTTP 404 Not Found. Knocknoc does not create the data-group; an administrator must create it (and the ...

Agent error code #F5052 indicates that the configured data-group exists, but it is not an Address (type ip) data-group. Knocknoc stores granted IPs as address records, so the target must be an address data-group. Common causes include: The data-group was crea...

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

Agent error code #202000 indicates that the agent could not establish a connection to the Fortinet firewall or FortiManager. The connection attempt failed before any authentication could take place. This error is distinct from authentication failures (#202001)...

Agent error code #202001 indicates that the agent was unable to authenticate with a Fortinet device (FortiGate or FortiManager). The device rejected the API token provided by the agent. This error is distinct from authorization failures (#202002), which occur ...

Agent error code #202002 indicates that the agent authenticated successfully with the Fortinet device (FortiGate or FortiManager), but the API user lacks the permissions required to perform the requested operation. The device rejected the request with a "forbi...

Agent error code #202003 indicates that the agent could not establish a secure connection to the Fortinet device because of a TLS/SSL certificate problem. The connection was rejected before any authentication or API request could take place. This error is dist...

Agent error code #202004 indicates that the agent attempted to connect to the Fortinet device but the connection timed out before a response was received. The agent waits up to 10 seconds for a response. This error is distinct from connection failures (#202000...