Search Results

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

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

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 connection is made. Steps to Re...

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

Each Knocknoc user has a limit on how many things can be signed in and holding access at the same time. When that limit is reached, the user is shown a Session limit reached screen and asked to disconnect one of their active sessions before they can continue. ...