Advanced Search
Search Results
100 total results found
PFS102 - Failed to Update pfSense Alias
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...
PFS103 - pfSense Alias Not Found
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...
PFS200 - Failed to Apply Pending pfSense Firewall Changes
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...
PFS400 - Invalid or Unexpected Response from pfSense
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...
MikroTik
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...
MIKRO000 - Failed to Connect to MikroTik
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...
MIKRO001 - MikroTik Authentication Failed
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 ...
MIKRO002 - MikroTik Authorization Failed
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...
MIKRO003 - MikroTik TLS/SSL Certificate Error
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...
MIKRO004 - MikroTik Connection Timed Out
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...
MIKRO005 - MikroTik REST API Not Available
Agent error code #MIKRO005 indicates that the agent reached the host but did not find the RouterOS REST API at the expected path. Either the REST API is disabled, the device is running an older RouterOS version that predates REST, or the hostname is pointing a...
MIKRO100 - Failed to List MikroTik Address-List Entries
Agent error code #MIKRO100 indicates that the agent could not read the firewall address-list it is supposed to manage. This is the first call the agent makes before either adding or removing an entry, so a failure here usually points at a permissions or REST a...
MIKRO101 - Failed to Add MikroTik Address-List Entry
Agent error code #MIKRO101 indicates that the agent could not add an entry to the firewall address-list. The user was authenticated but the PUT /rest/ip/firewall/address-list call failed. Common causes include: The user lacks the write policy on its group A s...
MIKRO102 - Failed to Remove MikroTik Address-List Entry
Agent error code #MIKRO102 indicates that the agent located an address-list entry to delete but the DELETE /rest/ip/firewall/address-list/<id> call failed. Common causes include: The user lacks the write policy on its group The entry was already removed by a...
MIKRO400 - Invalid Response From MikroTik
Agent error code #MIKRO400 indicates that the agent reached the RouterOS REST API and received a response, but the response did not match the expected shape. The most common case is a non-2xx HTTP status with a JSON body that included a message field. Less com...
OKTA000 - Failed to Connect to Okta
Agent error code #OKTA000 indicates that the agent could not reach the Okta REST API at the configured domain. The request failed before any authentication or network-zone operation could take place. This error is distinct from authentication failures (#OKTA00...
OKTA001 - Okta Authentication Failed
Agent error code #OKTA001 indicates that the Okta API rejected the API token in the agent's Authorization: SSWS <token> header. Okta returned HTTP 401 Unauthorized. This error is distinct from authorization failures (#OKTA002), which occur when the token is va...
OKTA002 - Okta Authorization Failed
Agent error code #OKTA002 indicates that the Okta API authenticated the agent's token but rejected the network-zone request with HTTP 403 Forbidden. The admin role behind the token lacks the permissions required to read or update network zones. This error is d...