Advanced Search
Search Results
365 total results found
MERA100 - Failed to Read the Meraki Policy Object Group
Agent error code #MERA100 indicates the agent could not read the configured policy object group. Common causes include: A transient Dashboard error or rate limit The Policy Object Group ID is incorrect (see #MERA102) Steps to Resolve Verify the Policy Object G...
MERA101 - Failed to Update the Meraki Policy Object Group
Agent error code #MERA101 indicates the agent could not update the membership of the configured policy object group. Common causes include: A transient Dashboard error or rate limit The API key's administrator lacks write access to policy objects Steps to Reso...
MERA102 - Meraki Policy Object Group Not Found
Agent error code #MERA102 indicates the configured policy object group could not be found (HTTP 404). Common causes include: The Policy Object Group ID is incorrect The group was deleted in the Meraki Dashboard Steps to Resolve In the Meraki Dashboard, go to O...
MERA150 - Failed to Create a Meraki Policy Object
Agent error code #MERA150 indicates the agent could not create the CIDR policy object for a granted IP. Common causes include: The organization has reached its policy object limit A transient Dashboard error or rate limit The API key's administrator lacks writ...
MERA151 - Failed to Delete a Meraki Policy Object
Agent error code #MERA151 indicates the agent removed an object from the group but could not delete the underlying policy object. The object is no longer enforced, but it remains in the organization as an orphan. Common causes include: A transient Dashboard er...
MERA152 - Failed to Read a Meraki Policy Object
Agent error code #MERA152 indicates the agent could not read a policy object referenced by the configured group. Common causes include: A transient Dashboard error or rate limit The object was deleted out-of-band between reading the group and reading the objec...
MERA400 - Invalid Response from the Meraki Dashboard
Agent error code #MERA400 indicates the Meraki Dashboard returned a response the agent could not parse. Common causes include: A proxy or captive portal returning HTML instead of the API response An unexpected API change Steps to Resolve Confirm requests reach...
Session limits and disconnecting sessions
Each Knocknoc user has a limit on how many things can be signed in and holding access at the same time. When that limit is reached, the user is shown a Session limit reached screen and asked to disconnect one of their active sessions before they can continue. ...
nftables
Knocknoc integrates with nftables to dynamically control network access on a Linux host. When a user authenticates, their IP address is added to an nftables named set, and removed again when their access ends. Your own rules reference that set with @setname t...
FSTL001 - Fastly Authentication Failed
Agent error code #FSTL001 indicates Fastly rejected the API token in the agent's Fastly-Key header (HTTP 401). This is distinct from an authorization failure (#FSTL002), where the token is valid but cannot reach the service. Common causes include: The token h...
FSTL002 - Fastly Authorization Failed
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...
FSTL003 - Fastly API TLS Error
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...
FSTL005 - Fastly API Rate Limit Exceeded
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...
FSTL050 - Failed to Read the Fastly Service
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 ...
FSTL051 - Fastly Service Not Found
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...
FSTL052 - The Fastly Service Has No Active Version
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...
FSTL100 - Failed to Read the Fastly ACL
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...
FSTL101 - Fastly ACL Not Found
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...