Advanced Search
Search Results
265 total results found
PFS005 - pfSense REST API Package Not Installed
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...
PFS100 - Failed to Get pfSense Alias
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...
PFS101 - Failed to Create pfSense Alias
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...
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...
PFS104 - pfSense Host Alias Cannot Hold a Network
Agent error code #PFS104 indicates that a grant carried a whole network as its source (a predefined source configured as a CIDR range, not a single address), but the pfSense alias this Knoc manages is typed Host(s). A host alias can only hold single IP address...
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...
PROX000 - Proxmox Authentication Failed
Agent error code #PROX000 indicates that Proxmox VE rejected the API token provided by the agent. The cluster returned HTTP 401 (Unauthorized). This error is distinct from authorization failures (#PROX001), which occur when the token is valid but lacks the req...
PROX001 - Proxmox Authorization Failed
Agent error code #PROX001 indicates that the Proxmox API authenticated the token successfully but rejected the requested action with HTTP 403 (Forbidden). The token lacks the privileges needed to read or modify the configured firewall ipset. This error is dist...
PROX002 - Proxmox Did Not Respond In Time
Agent error code #PROX002 indicates that the agent connected to Proxmox VE but the cluster did not return a response before the request timed out. Common causes include: The Proxmox host is under heavy load and is slow to answer API requests A firewall or netw...
PROX003 - Proxmox TLS Certificate Error
Agent error code #PROX003 indicates that the agent could not establish a trusted TLS connection to Proxmox VE. The certificate presented by the cluster could not be verified. By default Proxmox VE uses a self-signed certificate, which the agent will not trust ...
PROX004 - Connection Refused By Proxmox
Agent error code #PROX004 indicates that the agent reached the Proxmox host but the connection to the API port was actively refused. Nothing was listening on the address and port in the backend URL. Common causes include: The backend URL points at the wrong po...
PROX005 - Failed To Resolve Proxmox Hostname
Agent error code #PROX005 indicates that the agent could not resolve the Proxmox hostname in the backend URL to an IP address via DNS. Common causes include: A typo in the hostname configured in the Knocknoc backend The hostname is internal-only and the agent'...
PROX006 - Proxmox Request Failed
Agent error code #PROX006 indicates that a request to the Proxmox VE API failed at the network layer for a reason the agent could not classify more specifically. This is the catch-all transport error for Proxmox. If the agent could identify the cause it would ...
PROX100 - Proxmox Ipset Not Found
Agent error code #PROX100 indicates that the ipset configured in the Knocknoc ACL does not exist on the Proxmox VE cluster (or on the configured VM, for per-VM scope). The cluster returned HTTP 404 when the agent looked it up. This error is distinct from autho...
PROX101 - Failed To Read Proxmox Ipset Contents
Agent error code #PROX101 indicates that the agent reached Proxmox VE and the ipset lookup did not fail with a not-found or permission error, but the response could not be used to read the current ipset contents. This is distinct from #PROX100 (the ipset does ...
PROX102 - Failed To Add Entry To Proxmox Ipset
Agent error code #PROX102 indicates that the agent tried to add an IP address to the configured Proxmox VE ipset and Proxmox rejected the operation. The agent only adds and removes ipset entries. It does not create the ipset itself. If the ipset is missing the...