Search Results

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

Agent error code #PFS100 indicates that the request to read the alias from pfSense failed. This lookup is required before every grant and revocation, so this error blocks alias updates. This error is distinct from alias-not-found (#PFS103), which returns a cle...

Agent error code #PFS101 indicates that the agent attempted to create a new alias on pfSense (because the configured alias did not exist) and pfSense rejected the create request. This error is distinct from update failures (#PFS102), which occur on existing al...

Agent error code #PFS102 indicates that the agent attempted to update an existing alias on pfSense and the update request was rejected. This is the most common alias-edit failure and blocks any grant or revocation against the affected alias. This error is dist...

Agent error code #PFS103 indicates that the alias name configured in the Knocknoc ACL does not exist on pfSense. The agent looked the alias up and pfSense reported that no alias by that name is defined. This error is distinct from update failures (#PFS102), wh...

Agent error code #PFS200 indicates that the alias was updated successfully but the subsequent apply step failed. Without the apply, the change is held as pending and will not take effect against live firewall rules. This error is distinct from alias edit failu...

Agent error code #PFS400 indicates that the agent received a response from pfSense that it could not parse as a valid pfRest response. The call completed at the network level but the body was not in the expected format. This error is distinct from the more spe...

Knocknoc integrates with MikroTik RouterOS to dynamically control network access. The Knocknoc agent maintains a firewall address-list on the MikroTik device. As users authenticate and grants expire, the agent adds and removes entries in the list. Existing fir...

Agent error code #MIKRO000 indicates that the agent could not reach the MikroTik REST API. The request failed before any authentication or address-list operation could take place. This error is distinct from authentication failures (#MIKRO001), authorization f...

Agent error code #MIKRO001 indicates that the MikroTik device rejected the credentials supplied by the Knocknoc agent. The REST endpoint returned HTTP 401 Unauthorized. Common causes include: The Username or Password in the Knocknoc backend is wrong The user ...

Agent error code #MIKRO002 indicates that the MikroTik user authenticated successfully but lacks the permissions required to read or modify the firewall address-list. The REST endpoint returned HTTP 403 Forbidden. Common causes include: The user is in a group...

Agent error code #MIKRO003 indicates that the TLS handshake to the MikroTik REST API failed because the certificate could not be verified. Common causes include: RouterOS is presenting a self-signed certificate that the agent host does not trust The certifica...

Agent error code #MIKRO004 indicates that the network connection to the MikroTik REST API did not complete within the agent's timeout window. Common causes include: The router is reachable but overloaded or its CPU is saturated A firewall between the agent an...