Advanced Search
Search Results
265 total results found
OKTA050 - Failed to Get Okta Network Zone
Agent error code #OKTA050 indicates that the agent could not retrieve the configured network zone from Okta. The request reached Okta and authenticated successfully, but Okta returned an unexpected status (other than the 404 case covered by #OKTA052). Common c...
OKTA051 - Failed to Update Okta Network Zone
Agent error code #OKTA051 indicates that the agent retrieved the network zone successfully but the PUT to update its gateways was rejected by Okta. This is distinct from authentication failures (#OKTA001) and authorization failures (#OKTA002). At this point Ok...
OKTA052 - Okta Network Zone Not Found
Agent error code #OKTA052 indicates that Okta returned HTTP 404 for the configured Network Zone ID. The Knocknoc backend points at a network zone that no longer exists in the org. Common causes include: The network zone was deleted in the Okta admin console Th...
OKTA053 - Okta Network Zone Is Not an IP Zone
Agent error code #OKTA053 indicates that the configured network zone exists, but its type is not IP. Knocknoc only manages IP zones. Dynamic zones (geolocation, ASN, anonymiser) and policy-network zones are not supported. Common causes include: The zone was ...
OKTA054 - Invalid or Unexpected Response from Okta
Agent error code #OKTA054 indicates that Okta returned a 2xx status, but the response body did not match the expected schema. The agent could not decode the network-zone response. This error is rare. It usually points at something sitting between the agent and...
OPN000 - OPNsense Authentication Failed
Agent error code #OPN000 indicates that the OPNsense API rejected the credentials provided by the agent. The firewall returned HTTP 401 (Unauthorized). This error is distinct from authorization failures (#OPN001), which occur when the credentials are valid but...
OPN001 - OPNsense Authorization Failed
Agent error code #OPN001 indicates that the agent authenticated with OPNsense successfully, but the API user lacks the privileges required to manage aliases. OPNsense returned HTTP 403 (Forbidden). This error is distinct from authentication failures (#OPN000),...
OPN002 - OPNsense Request Timed Out
Agent error code #OPN002 indicates that an OPNsense API call did not complete within the agent's timeout window. The firewall accepted the connection but did not return a response in time. This error is distinct from connection failures (#OPN004) and DNS failu...
OPN003 - OPNsense TLS Certificate Error
Agent error code #OPN003 indicates that the agent could not verify the TLS certificate presented by OPNsense. The TLS handshake failed before any API request could be sent. This error is distinct from connection refused (#OPN004) or timeout (#OPN002) errors. E...
OPN004 - Connection Refused by OPNsense
Agent error code #OPN004 indicates that the OPNsense host actively refused the connection from the agent. The TCP handshake reached the host but no service was listening on the requested port. This error is distinct from timeouts (#OPN002), which mean the host...
OPN005 - Cannot Resolve OPNsense Hostname
Agent error code #OPN005 indicates that the agent host could not resolve the OPNsense hostname to an IP address. The request failed before any network connection was attempted. This error is distinct from connection refused (#OPN004) and timeout (#OPN002), whi...
OPN006 - OPNsense Request Failed
Agent error code #OPN006 is the fallback code for OPNsense API errors that don't match a more specific classification. The agent reached the firewall and the call completed, but the response indicated a transport-level or unclassified failure. This error is di...
OPN100 - OPNsense Alias Not Found
Agent error code #OPN100 indicates that the alias name configured in the Knocknoc ACL does not exist on OPNsense. The firewall returned HTTP 404 when the agent looked up the alias. This error is distinct from authorization failures (#OPN001), which occur when ...
OPN101 - Failed to Read OPNsense Alias Contents
Agent error code #OPN101 indicates that the agent could reach the alias listing endpoint on OPNsense but the response was unexpected (non-2xx HTTP status or malformed body). The lookup is required before every grant and revocation, so this error blocks alias u...
OPN102 - Failed to Add Entry to OPNsense Alias
Agent error code #OPN102 indicates that OPNsense rejected an attempt to add an entry to the configured alias. The agent located the alias successfully but the add request did not complete. This error is distinct from authorization failures (#OPN001), which pre...
OPN103 - Failed to Remove Entry from OPNsense Alias
Agent error code #OPN103 indicates that OPNsense rejected an attempt to remove an entry from the configured alias. The agent located the alias successfully but the delete request did not complete. This error is distinct from authorization failures (#OPN001), w...
OPN200 - Failed to Apply OPNsense Alias Changes
Agent error code #OPN200 indicates that the alias entry was added or removed successfully, but the subsequent apply step failed. Without the apply, the change is not persisted to the saved configuration and will be lost on the next filter reload. This error is...
200000 - Target Firewall Not Connected to Panorama
This error occurs when the Knocknoc agent attempts to refresh an External Dynamic List (EDL) on a Palo Alto Networks firewall through Panorama, but the target firewall cannot be reached. Common causes include: The firewall is not connected to Panorama (it may ...