Search Results

Agent error code #FSTL002 indicates the API token authenticated but is not allowed to act on the configured service (HTTP 403). The Knoc wizard's Validate connection step reads the token's own record, so a read-only token is reported here rather than at the fi...

Agent error code #FSTL003 indicates the TLS handshake with the Fastly API failed: the certificate could not be verified, was invalid, or did not match the host. Common causes include: A TLS-inspecting proxy presents its own certificate and its CA is not in the...

Agent error code #FSTL005 indicates Fastly answered with HTTP 429: the API token has made too many requests. The agent already retries a 429 a few times, honoring the Retry-After header, so this code means the limit was still in force after those retries. Com...

Agent error code #FSTL050 indicates the agent could not read the configured Fastly service. It reads the service to find the active version, which is where the ACL lives. Common causes include: The Service ID is wrong (see also #FSTL051) The token cannot read ...

Agent error code #FSTL051 indicates Fastly answered HTTP 404 for the configured service. Common causes include: The Service ID has a typo, or a service name was entered instead of its ID The service was deleted The token belongs to a different Fastly account S...

Agent error code #FSTL052 indicates the configured service has no active version, so its ACLs are not in force and there is nothing for Knocknoc to write into. Common causes include: The service was created but never activated Every version was deactivated dur...

Agent error code #FSTL100 indicates the agent could not list the ACLs on the service's active version, so it could not resolve the configured ACL name to an ACL. Common causes include: The token can read the service but not its versioned configuration A transi...

Agent error code #FSTL101 indicates no ACL with the configured name exists on the service's active version. Knocknoc looks the ACL up by name on every fresh resolve, so this also fires when an ACL was deleted and its replacement was never activated. Common cau...

Agent error code #FSTL150 indicates Fastly refused to add the entry for a granted address, so the user has not been allowed through. An address the ACL already holds is not an error: Knocknoc treats a duplicate as a successful grant. A full ACL reports #FSTL15...

Agent error code #FSTL151 indicates Fastly refused to remove an entry, so an address may still be allowed through after its grant ended. An entry that is already gone is not an error: Knocknoc treats it as a completed revoke. Common causes include: The token c...

Agent error code #FSTL152 indicates the agent could not read the ACL's entries. It reads them to find the entry to remove on a revoke, and to reconcile its own view of the ACL. Common causes include: The token lost access to the service The ACL was deleted (se...

Agent error code #FSTL153 indicates the ACL is full, so the grant could not be added. Fastly caps an ACL at 1,000 entries and documents no self-service way to raise it. Unlike a rate limit (#FSTL005), waiting does not clear this. Something has to leave the ACL...

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