Search Results

Agent error code #203150 indicates that the agent attempted to update a GCP resource multiple times but each attempt failed due to a fingerprint conflict (HTTP 409 or 412). The agent exhausted its retry limit. GCP uses fingerprints (ETags) for optimistic concu...

Agent error code #203151 indicates that the GCP API returned HTTP 404 (Not Found) when the agent attempted to access a firewall rule or security policy rule. The specified resource does not exist in the configured GCP project. This error is typically surfaced ...

Agent error code #205001 means the agent encountered a filesystem error while reading the nginx allow/deny include file. Steps to Resolve Confirm the file is owned (or at least readable) by the knocknoc-agent user: sudo chown knocknoc-agent /etc/nginx/acl/my...

Agent error code #205002 means the agent could not rewrite the nginx allow/deny include file. The agent writes to a temp file in the same directory and renames it into place; both steps must succeed. Steps to Resolve Ensure /etc/nginx/acl/ exists on the agen...

Agent error code #205050 means the agent ran sudo -n nginx -s reload after editing the include file, but the reload failed. The new ACL is on disk; nginx has not picked it up yet. Steps to Resolve Run sudo nginx -t on the agent host to check the running conf...

Agent error code #298000 indicates that the agent failed to refresh an External Dynamic List (EDL) or dynamic external object on a firewall, for reasons that don't fall into more specific error categories. This error typically occurs when: The configured EDL ...

Agent error code #298001 indicates that the agent attempted to connect to a firewall to refresh an external object (such as an External Dynamic List or dynamic group), but the connection timed out before a response was received. This error occurs when the agen...

Agent error code #298002 indicates that the agent encountered a TLS/SSL certificate error when attempting to connect to a firewall. The secure connection could not be established because the certificate presented by the firewall failed validation. This error o...

Agent error code #298003 indicates that the agent failed to authenticate with a firewall when attempting to refresh an external object (such as an External Dynamic List or dynamic group). The firewall rejected the credentials provided by the agent. This error ...

Agent error code #298004 indicates that the agent successfully authenticated with the firewall, but lacks the necessary permissions to perform the requested operation. This error is distinct from authentication errors (#298003): TODO, where the credentials the...

Agent error code #298005 indicates that the agent attempted to connect to a firewall, but the connection was actively refused. The firewall's host is reachable, but nothing is listening on the specified port, or a firewall rule is blocking the connection. This...

Agent error code #298006 indicates that the agent could not resolve the hostname configured for a firewall. The agent attempted to look up the firewall's hostname but the DNS query failed. This error is distinct from connection refused (#298005): TODO or timeo...

Agent error code #PFS000 indicates that the agent could not reach the pfSense REST API at all. The request failed before any authentication or alias operation could take place. This error is distinct from authentication failures (#PFS001), authorization failur...

Agent error code #PFS001 indicates that the pfSense REST API rejected the credentials provided by the agent. The API returned HTTP 401 (Unauthorized). This error is distinct from authorization failures (#PFS002), which occur when the credentials are valid but ...

Agent error code #PFS002 indicates that the agent authenticated to pfSense successfully but the API user lacks the privileges required to manage aliases. pfSense returned HTTP 403 (Forbidden). This error is distinct from authentication failures (#PFS001), whic...

Agent error code #PFS003 indicates that the agent could not verify the TLS certificate presented by pfSense. The TLS handshake failed before any API request could be sent. This error is distinct from connection refused or timeout errors (#PFS000, #PFS004). Err...

Agent error code #PFS004 indicates that a pfSense API call did not complete within the agent's timeout window. The connection was established but pfSense did not return a response in time. This error is distinct from connection failures (#PFS000), which occur ...

Agent error code #PFS005 indicates that the agent connected to pfSense successfully but the pfRest REST API package is not installed or not enabled. None of Knocknoc's alias operations work without it. This error is distinct from connection or authentication f...