Search Results

Knocknoc integrates with Fastly to control which source IPs an edge service lets through. The integration writes entries into an existing Fastly ACL on a service's active version. The orchestration is performed by a Knocknoc orchestration Agent which is subscr...

Agent error code #FSTL000 indicates the agent could not reach the Fastly API. The connection was never established, so nothing was written. This is distinct from authentication failures (#FSTL001), authorization failures (#FSTL002), TLS errors (#FSTL003) and t...

Agent error code #FSTL004 indicates the Fastly API did not answer within the agent's timeout. Common causes include: Packet loss or a saturated link between the agent and Fastly A proxy holding the connection open without forwarding it A Fastly incident Steps ...

Agent error code #FSTL400 indicates the API answered successfully but the body was not the JSON the agent expected. Common causes include: An API base URL override points at a proxy, captive portal or login page that answers 200 with HTML A TLS-inspecting prox...

Agent error code #AWS000 indicates that the agent could not find the aws binary on the host it is running on. The AWS backend drives EC2 security groups by shelling out to the AWS CLI, so without it no grant can be applied. Common causes include: The AWS CLI ...

Agent error code #AWS001 indicates that AWS rejected the agent's credentials. The request reached AWS and was refused before any permission check took place. AWS returns AuthFailure, InvalidClientTokenId or SignatureDoesNotMatch in this situation, which is ...

Agent error code #AWS002 indicates that AWS accepted the agent's credentials but refused the operation. The identity is valid and lacks the permission the call needs. AWS returns UnauthorizedOperation or AccessDenied in this situation, which is worth knowing...

Agent error code #AWS003 indicates that AWS rate-limited the request. AWS returns Throttling or RequestLimitExceeded in this situation. This is a transient condition. The grant is retried, and in most cases it succeeds on a later attempt without any action. ...

Agent error code #AWS050 indicates that AWS could not find the security group configured on the knoc. AWS returns InvalidGroup.NotFound or InvalidGroupId.Malformed in this situation. Common causes include: The security group was deleted after the knoc was co...

Agent error code #AWS051 indicates that AWS refused a value in the request. AWS returns InvalidParameterValue, InvalidParameter or MalformedInput in this situation. The credentials and the security group were both accepted. Something in the rule the agent t...

Agent error code #AWS100 indicates that Knocknoc could not read the current rules on the security group. This read runs before any change is made to the group, so the grant stops here. More specific causes report their own codes: rejected credentials report #A...

Agent error code #AWS101 indicates that the call adding a rule to the security group failed for a reason the agent could not attribute to a more specific cause. This is the operation that grants a user access. More specific causes report their own codes: rejec...

Agent error code #AWS102 indicates that the call removing a rule from the security group failed. Access that should have been withdrawn may still be in place. More specific causes report their own codes: rejected credentials report #AWS001, a missing permissio...

Agent error code #204000 indicates that the agent could not find the az binary on the host it is running on. The Azure NSG backend drives network security groups by shelling out to the Azure CLI, so without it no grant can be applied. Common causes include: T...

Agent error code #204001 indicates that az login --service-principal failed. The agent authenticates to Azure with a service principal before every group of NSG operations, and Entra ID refused it. Common causes include: The client ID, client secret or tenant...

Agent error code #204050 indicates that Knocknoc could not read the rules on the network security group, or read them and could not parse the response. This read runs before any change is made to the NSG, so the grant stops here. Common causes include: The NSG...