Skip to main content

203151 - GCP Resource Not Found

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 within a resource-specific error (#203050, #203051, #203100, or #203101) that provides additional context about which operation failed.

Common causes include:

  • The firewall rule name or security policy name configured in Knocknoc is incorrect or has a typo
  • The resource was deleted from GCP after the Knocknoc backend was configured
  • The GCP Project ID is wrong — the resource exists in a different project
  • For Cloud Armor, the security policy exists but no rule exists at the configured priority number
  • The resource name is case-sensitive and does not match exactly

Steps to Resolve

Verify the Resource Exists in GCP

For VPC Firewall mode:

  1. In the GCP Console, navigate to VPC Network > Firewall
  2. Confirm a firewall rule exists with the exact name configured in the Knocknoc ACL
  3. Rule names are lowercase and may contain hyphens (e.g., knocknoc-allow-ssh)

For Cloud Armor mode:

  1. In the GCP Console, navigate to Network Security > Cloud Armor
  2. Confirm the security policy exists with the exact name configured in the Knocknoc ACL
  3. Open the policy and confirm a rule exists at the exact priority number configured in Knocknoc

Verify the GCP Project ID

  1. In the Knocknoc admin interface, check the backend configuration
  2. Confirm the GCP Project ID matches the project where the resource exists
  3. Find your project ID in the GCP Console dashboard or project selector — note that the project ID is not the same as the project name or number

Recreate the Resource

If the resource was deleted, recreate it following the setup guide:

Back to top