Advanced Search
Search Results
265 total results found
200200 - Failed to Check HA State
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...
200201 - Neither Firewall in the HA Pair Is Active
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...
200250 - Firewall or Panorama Mismatch
Agent error code #200250 means the address in the integration belongs to a different kind of device than the integration is set up for. Either it points at a Panorama with Use Panorama off, or at a firewall with Use Panorama on. Knocknoc talks to the two diffe...
200251 - Managed Firewall Not Found or Not Connected
Agent error code #200251 means a serial number on the knoc does not match a firewall Panorama manages, or matches one that is not connected to Panorama right now. Through Panorama, Knocknoc sends each change to the managed firewalls named on the knoc. A serial...
200252 - Device Group Not Found
Agent error code #200252 means the device group on the knoc does not exist on Panorama, or one of the knoc's managed firewalls is not a member of it. In address group mode through Panorama, Knocknoc writes its address objects into the device group, and Panoram...
200253 - External Dynamic List Not Found
Agent error code #200253 means the firewall has no IP external dynamic list with the name configured on the knoc. In Passive+ mode, a grant asks the firewall to refresh the list straight away, so a new address is picked up in seconds rather than at the list's ...
200254 - Firewall Cannot Fetch the External Dynamic List
Agent error code #200254 means the firewall has the external dynamic list, but reports that its last attempt to fetch the list failed. Until it succeeds, the firewall keeps using whatever it last fetched, so newly granted users are not admitted. The firewall f...
200255 - Address Group Is a Dynamic Group
Agent error code #200255 means the address group on the knoc is a dynamic address group, which matches addresses by tag. In address group mode, Knocknoc adds address objects to a static group's member list, and a dynamic group has no member list to add to. Ste...
200256 - No Dynamic Address Group Matches the Tag
Agent error code #200256 is a warning from Validate. The agent looked for a dynamic address group whose match criteria name the knoc's tag, and found none where it looked. A registration on a tag no group matches is accepted by the firewall but admits nobody. ...
200257 - Tag Already Carries Registrations
Agent error code #200257 is a warning from Validate on a knoc that has not been saved yet. The tag it names already has addresses registered on the firewall. A tag belongs to one knoc. Knocknoc reads back what is registered on the tag and removes any address t...
200258 - Address Group Mode Needs PAN-OS 10.2
Agent error code #200258 means the device runs a PAN-OS release older than 10.2. Address group mode creates address objects and edits the group through the PAN-OS REST API version 10.2, which older releases do not offer. Through Panorama, the release that matt...
200300 - API Key Not Returned
Agent error code #200300 means Generate key on the Integrations page reached the device but did not get an API key back. Nothing was saved, and the integration still holds whatever key it had before. Common causes include: The address points at something other...
200301 - Generate Key Credentials Refused
Agent error code #200301 means Generate key on the Integrations page reached the device and the device refused the username or password. Knocknoc does not keep either, so nothing needs cleaning up. Common causes include: The username or password was mistyped, ...
PFS000 - Failed to Connect to pfSense
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...
PFS001 - pfSense Authentication Failed
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 ...
PFS002 - pfSense Authorization Failed
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...
PFS003 - pfSense TLS/SSL Certificate Error
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...
PFS004 - pfSense Connection Timed Out
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 ...