Search Results

Agent error code #MIKRO005 indicates that the agent reached the host but did not find the RouterOS REST API at the expected path. Either the REST API is disabled, the device is running an older RouterOS version that predates REST, or the hostname is pointing a...

Agent error code #MIKRO100 indicates that the agent could not read the firewall address-list it is supposed to manage. This is the first call the agent makes before either adding or removing an entry, so a failure here usually points at a permissions or REST a...

Agent error code #MIKRO101 indicates that the agent could not add an entry to the firewall address-list. The user was authenticated but the PUT /rest/ip/firewall/address-list call failed. Common causes include: The user lacks the write policy on its group A s...

Agent error code #MIKRO102 indicates that the agent located an address-list entry to delete but the DELETE /rest/ip/firewall/address-list/<id> call failed. Common causes include: The user lacks the write policy on its group The entry was already removed by an...

Agent error code #MIKRO400 indicates that the agent reached the RouterOS REST API and received a response, but the response did not match the expected shape. The most common case is a non-2xx HTTP status with a JSON body that included a message field. Less com...

Agent error code #OKTA000 indicates that the agent could not reach the Okta REST API at the configured domain. The request failed before any authentication or network-zone operation could take place. This error is distinct from authentication failures (#OKTA00...

Agent error code #OKTA001 indicates that the Okta API rejected the API token in the agent's Authorization: SSWS <token> header. Okta returned HTTP 401 Unauthorized. This error is distinct from authorization failures (#OKTA002), which occur when the token is va...

Agent error code #OKTA002 indicates that the Okta API authenticated the agent's token but rejected the network-zone request with HTTP 403 Forbidden. The admin role behind the token lacks the permissions required to read or update network zones. This error is d...

Agent error code #OKTA003 indicates that the agent's TLS handshake with the configured Okta domain failed. The certificate presented by the endpoint could not be verified against the system trust store. This error is distinct from connection failures (#OKTA000...

Agent error code #OKTA004 indicates that a request to the configured Okta domain did not complete within the agent's HTTP timeout. This error is distinct from connection failures (#OKTA000), which mean the connection never established at all. Error #OKTA004 me...

Agent error code #OKTA005 indicates that Okta rejected the request with HTTP 429 Too Many Requests. The agent has hit the per-org rate limit on the network-zones API. Okta publishes its rate limits at Okta rate limits. The network-zones endpoint shares a bucke...

Agent error code #OKTA050 indicates that the agent could not retrieve the configured network zone from Okta. The request reached Okta and authenticated successfully, but Okta returned an unexpected status (other than the 404 case covered by #OKTA052). Common c...

Agent error code #OKTA051 indicates that the agent retrieved the network zone successfully but the PUT to update its gateways was rejected by Okta. This is distinct from authentication failures (#OKTA001) and authorization failures (#OKTA002). At this point Ok...

Agent error code #OKTA052 indicates that Okta returned HTTP 404 for the configured Network Zone ID. The Knocknoc backend points at a network zone that no longer exists in the org. Common causes include: The network zone was deleted in the Okta admin console T...

Agent error code #OKTA053 indicates that the configured network zone exists, but its type is not IP. Knocknoc only manages IP zones. Dynamic zones (geolocation, ASN, anonymiser) and policy-network zones are not supported. Common causes include: The zone was c...

Agent error code #OKTA054 indicates that Okta returned a 2xx status, but the response body did not match the expected schema. The agent could not decode the network-zone response. This error is rare. It usually points at something sitting between the agent and...