Search Results

Agent error code #CHKP005 indicates that the Check Point gateway refused the request with a bare HTTP 404 or 403 and no specific error code in the body. The gateway gives the same response whether the shared secret is wrong or the agent's source IP is not auth...

Agent error code #CHKP050 indicates that the Knocknoc agent's request to register a user's identity on the Check Point gateway was rejected, and the rejection did not match a more specific cause. This is the generic "push failed" code. When Knocknoc can identi...

Agent error code #CHKP051 indicates that the Knocknoc agent's request to remove a user's identity from the Check Point gateway was rejected on grant revocation or logout. A "not found" response on removal is not treated as this error. If the identity is alread...

Agent error code #CHKP052 indicates that the Access Role configured on the Knoc does not correspond to an Access Role object on the Check Point gateway. Knocknoc never creates or modifies Access Roles. It only assigns an existing role to authenticated user IPs...

Agent error code #CHKP053 indicates that the Check Point gateway's response showed the Identity Awareness blade is not active. Without that blade the Identity Web API is not served, so Knocknoc cannot register identities. A bare 404 or 403 without a clear "ide...

Agent error code #CHKP054 indicates that the per-identity session timeout Knocknoc sent with the identity was below the minimum the Check Point gateway will accept. The gateway rejected the registration as a result. When Knocknoc registers an identity it sets ...

Agent error code #CHKP400 indicates that the Knocknoc agent received a response from the configured endpoint that it could not parse as an Identity Web API reply. This almost always means the Gateway Hostname or its port is pointing at something that is not th...

Agent error code #CHKP401 indicates that the Check Point gateway returned a server error (HTTP 5xx) in response to an Identity Web API request. The request reached the API but the gateway failed to process it on its side. Unlike the 4xx-class errors, this is a...

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

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

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

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

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

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

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

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

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

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