Advanced Search
Search Results
389 total results found
Kemp LoadMaster
Knocknoc integrates with the Kemp LoadMaster to dynamically control network access. Knocknoc dynamically manages the LoadMaster's global allowlist. As users authenticate and grants expire, Knocknoc adds and removes entries in the allowlist, so access is grante...
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...
PROX103 - Failed To Remove Entry From Proxmox Ipset
Agent error code #PROX103 indicates that the agent tried to remove an IP address from the configured Proxmox VE ipset and Proxmox rejected the operation. The agent only adds and removes ipset entries. If the ipset is missing the agent returns #PROX100 instead....
PROX104 - Proxmox Node Or VM Not Found
Agent error code #PROX104 indicates that, for a per-VM (qemu) scoped Knoc, Proxmox VE could not find the node or VM the agent was directed to. This applies only to per-VM scope. For cluster-scoped Knocs the agent does not target a node or VM, and a missing ips...
PROX400 - Invalid Response From Proxmox
Agent error code #PROX400 indicates that the agent received a response from Proxmox VE that it could not parse as the expected ipset data. The request reached Proxmox, but the body was not in the form the agent expected. Common causes include: The backend URL ...
KEMP000 - Failed to Connect to Kemp LoadMaster
Agent error code #KEMP000 indicates that Knocknoc could not reach the Kemp LoadMaster API. The connection could not be established. This error is distinct from authentication failures (#KEMP001), authorization failures (#KEMP002), TLS errors (#KEMP003), timeou...
KEMP001 - Kemp LoadMaster Authentication Failed
Agent error code #KEMP001 indicates that Knocknoc reached the Kemp LoadMaster but the username or password was rejected. The API returned HTTP 401 Unauthorized. This is distinct from an authorization failure (#KEMP002), where the credentials are valid but the ...
KEMP002 - Kemp LoadMaster Authorization Failed
Agent error code #KEMP002 indicates that the credentials authenticated successfully but the user lacks the permissions required to read or modify the global ACL. The API returned HTTP 403 Forbidden. Common causes include: The user account does not have All Per...
KEMP003 - Kemp LoadMaster TLS/SSL Certificate Error
Agent error code #KEMP003 indicates that Knocknoc could not establish a trusted TLS connection to the Kemp LoadMaster. The LoadMaster's certificate could not be verified against Knocknoc host's trust store. LoadMasters often ship with a self-signed management ...