Search Results

Knocknoc 26.03 Knocknoc 26.03 is a major usability-and-operations release focused on making day-to-day access clearer and easier to understand - for both end-users requesting access and administrators running the platform. A far stronger operational experience...

Knocknoc 26.04 Knocknoc 26.04.1 is a size-optimized release focused on expanding deployment flexibility, improving firewall and cloud integration options, refining installation workflows, and shipping some small bug fixes. This release introduces Google GCP or...

Knocknoc 26.05 Knocknoc 26.05 brings threat intelligence blocking integration, expanded cloud and platform support, live configuration validation, and streamlined authentication workflow for a more seamless end-user access experience and more. 🚀 GreyNoise real...

Agent error code #203000 indicates that the agent could not communicate with the Google Cloud Platform Compute Engine API. The request failed before any authentication or resource operation could take place. This error is distinct from authentication failures ...

Agent error code #203001 indicates that the GCP API rejected the credentials provided by the agent. The API returned HTTP 401 (Unauthorized). This error is distinct from authorization failures (#203002), which occur when the credentials are valid but lack suff...

Agent error code #203002 indicates that the agent authenticated successfully with GCP, but the service account lacks the permissions required to perform the requested operation. The API returned HTTP 403 (Forbidden). This error is distinct from authentication ...

Agent error code #203003 indicates that the agent's request to the GCP Compute Engine API timed out before receiving a response. This can be a network-level timeout or an HTTP 408/504 response from the API. This error is distinct from general connection failur...

Agent error code #203050 indicates that the agent could not retrieve the VPC firewall rule from GCP. The error message includes additional detail about the underlying cause (e.g., authentication, authorization, resource not found, or timeout). This error occur...

Agent error code #203051 indicates that the agent could not update (patch) the VPC firewall rule in GCP. The error message includes additional detail about the underlying cause (e.g., authentication, authorization, or timeout). This error occurs during the PAT...

Agent error code #203100 indicates that the agent could not retrieve the Cloud Armor security policy rule from GCP. The error message includes additional detail about the underlying cause (e.g., authentication, authorization, resource not found, or timeout). T...

Agent error code #203101 indicates that the agent could not update (patch) the Cloud Armor security policy rule in GCP. The error message includes additional detail about the underlying cause (e.g., authentication, authorization, or timeout). This error occurs...

Agent error code #203150 indicates that the agent attempted to update a GCP resource multiple times but each attempt failed due to a fingerprint conflict (HTTP 409 or 412). The agent exhausted its retry limit. GCP uses fingerprints (ETags) for optimistic concu...

Agent error code #203151 indicates that the GCP API returned HTTP 404 (Not Found) when the agent attempted to access a firewall rule or security policy rule. The specified resource does not exist in the configured GCP project. This error is typically surfaced ...

Agent error code #205001 means the agent encountered a filesystem error while reading the nginx allow/deny include file. Steps to Resolve Confirm the file is owned (or at least readable) by the knocknoc-agent user: sudo chown knocknoc-agent /etc/nginx/acl/my...

Agent error code #205002 means the agent could not rewrite the nginx allow/deny include file. The agent writes to a temp file in the same directory and renames it into place; both steps must succeed. Steps to Resolve Ensure /etc/nginx/acl/ exists on the agen...

Agent error code #205050 means the agent ran sudo -n nginx -s reload after editing the include file, but the reload failed. The new ACL is on disk; nginx has not picked it up yet. Steps to Resolve Run sudo nginx -t on the agent host to check the running conf...