--- title: "Admin dashboard messages" slug: "admin-messages-v7-0" description: "Descriptions of warning and error messages that appear on the AppGate ZTNA Collective dashboard." tags: ["Admin UI", "Dashboard"] updated: 2026-10-01T20:20:57Z published: 2026-10-01T20:20:57Z canonical: "support.appgate.com/admin-messages-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Admin dashboard messages The dashboard includes a message feed. Messages typically relate to the configuration of the AppGate ZTNA Collective, a related system, or the network environment. The following table describes each message, its source, and the action to take: | Source | Error Level | Message | Action | | --- | --- | --- | --- | | Controller | Warning | A user did not get the entitlement `<Entitlement Name>` because it doesn't have a Site assigned. | Go to Access > Entitlements and select the named entitlement. Confirm that it has a valid Site assigned. | | Controller | Warning | A user did not get the entitlement, because its Site `<Site Name>` doesn't have any active Gateways assigned. | The Site assigned to the entitlement has no active Gateways. Go to System > Appliances and either seed a new Gateway or select an existing one and assign the correct Site to it. | | Controller | Warning | A user on identity provider `<Identity Provider Name>` received one or more Site routes from `<Site Name>` that is IPv(4/6) but did not get an IP allocated for it. Consider assigning an IPv(4/6) pool to the identity provider. | If IPv6 entitlements are in use but the identity provider has no IPv6 pool assigned, users cannot reach those entitlements. Assign the appropriate IP pool to the identity provider. | | Controller | Warning | Administrative API requests are being made to hostname `<IP/hostname>` instead of this Controller’s admin hostname by `<user agent string and IP address>`. This can cause system instability. Please update the client making these requests, such as a browser, script, or other integration to use the Controller admin hostname. | This message appears when an administrator or API script accesses the Controller using an IP that does not match the configured hostname. To prevent data instability, always target a single, specific Controller for administrative operations, as making changes across multiple Controllers simultaneously can cause instability. | | Controller | Warning | At least one of your policies is configured with override Site using the claim `<Claim Name>`, but that claim could not be found. Please review your policies. | Check the claim name in all policies that use ***Override using a claim***. Either correct the claim in the identity provider mapping or update the claim name in the policy's override Site setting. | | Controller | Warning | At least one of your policies is configured with override Site using the claim `<Claim Name>`, but that claim does not contain a UUID. Please review your policies. | Confirm that the claim contains the correct Site UUID. To find the Site UUID, go to the Site settings and copy the UUID from the admin UI URL. | | Controller | Warning | Client profile settings are defined in more than one active policy for a user. The setting from `<Policy name>` is being used because it comes first alphabetically. | One or more users have a conflicting client profile setting across their device policies. Identify which user has `<Policy name>` assigned, go to their session details, and run ***Analyze Policy Assignments***. This shows which items are conflicting. Update the access criteria to resolve the conflict. | | Controller | Warning | Client settings are defined in more than one active policy for a user. The setting from policy `<Policy name>` is being used because it comes first alphabetically. | One or more users have a conflicting client settings configuration across their policies. This most commonly occurs in device policies or the device section of mixed policies. Identify which user has `<Policy name>` assigned, go to their session details, and run ***Analyze Policy Assignments***. This shows which items are conflicting. Update the access criteria to resolve the conflict. | | Controller | Error | Controller has failed to verify metered EC2 instance state. Failures lasting longer than one hour prevent users signing in on this Controller. Details: `<AWS message>` | This error occurs only with metered subscription instances from AWS. The Controller cannot reach the AWS metered subscription API and cannot use the metered license model. Users attempting to sign in after one hour are affected. Users already connected are not affected. | | Controller | Warning | Criteria script `<Criteria Script Name>` for Client Auto-Update is not available. Reassign it to an existing criteria script in order to fix this issue. | The criteria script used to select users for the client auto-update service no longer exists. Go to System > Client Auto-Update and select an existing criteria script. | | Controller | Warning | Device Proxy Auto Config URL matches are defined in more than one active policy for a user. The setting from the policy `<Policy name>` is being used because it comes first alphabetically. | One or more users have a conflicting Device Proxy Auto Config URL setting across their policies. This most commonly occurs in device policies or the device section of mixed policies. Identify which user has `<Policy name>` assigned, go to their session details, and run ***Analyze Policy Assignments***. This shows which items are conflicting. Update the access criteria to resolve the conflict. | | Controller | Warning | `<Distinguished Name>` was unable to sign in as admin because there was no policy match. | Confirm that a valid admin policy is matched for this user. If no admin policy is active, see the knowledge base for remediation steps. | | Controller | Warning | Failed to allocate IP from pool `<IP Pool name>`: `<message>` | The Controller could not assign an IP from the pool to a user. In most cases, the IP pool is full on this Controller. If only one Controller is reporting this error and the IP pool list shows available IPs, confirm that users can reach all Controllers. Each Controller is responsible for allocating its share of the IP pool. | | Controller | Warning | Failed to map to IP pool `<IP Pool name>` because it doesn't exist. Mapping is defined on Site `<Site name>`. | The Controller could not map the tunnel IP to the mapped IP pool for <`Site name>`. Confirm that the mapping is configured correctly in the Site settings and that the mapped IP pool has available IPs. | | Controller | Warning | Failed to retrieve details from the identity provider `<Identity Provider Name>`. Please check the configuration and connectivity. | The Controller cannot communicate with the identity provider. Verify the identity provider settings, certificates, and connectivity between the Controller and the identity provider. | | Controller | Warning | Identity provider `<Identity Provider>` does not have IP pool assigned. | The identity provider has no IP pool assigned. Users can authenticate against the identity provider but receive an error because the Controller cannot assign a tunnel IP. Assign an IP pool to the identity provider. | | Controller | Error | Identity Provider `<Identity Provider Name>` has failed to authenticate a user. Details: `<Message>` | The identity provider failed to authenticate a user. Review the message details to determine why the user could not sign in, then investigate the identity provider configuration. | | Controller | Warning | Multiple active policies for a user have defined DNS settings for the same domain name `<domain>`. The setting from policy `<Policy name>` is being used because it comes first alphabetically. | One or more users have a conflicting DNS domain setting across their DNS policies. Identify which user has `<Policy name>` assigned, go to their session details, and run ***Analyze Policy Assignments***. This shows which items are conflicting. Update the access criteria to resolve the conflict. | | Controller | Warning | Multiple custom help URLs are defined in more than one active policy for a user. The setting from policy `<Policy name>` is being used because it comes first alphabetically. | One or more users have a conflicting custom help URL setting across their device policies. Identify which user has `<Policy name>` assigned, go to their session details, and run ***Analyze Policy Assignments***. This shows which items are conflicting. Update the access criteria to resolve the conflict. | | Controller | Warning | One or more of your licenses has an error. Please check your licenses and remove the ones with errors. | One of the uploaded licenses is incorrect or expired. Sign in to the admin UI, go to Settings > Licenses, and verify that all licenses are valid. If a license is incorrect, [contact support](/v1/docs/contact-support). | | Controller | Warning | One or more policy override Sites could not be found while trying to apply to entitlement `<Entitlement Name>`. Please review your policies. | Identify which policy has an assignment for the named entitlement, either directly or via tag. Confirm that the specified override Site still exists. | | Controller | Warning | One or more policy override Sites could not be found while trying to apply to entitlement `<Entitlement Name>`. Please review your policies. | More than one policy matches the named entitlement and each specifies a different override Site. Update the criteria scripts for all conflicting policies to resolve the conflict. | | Controller | Warning | Some entitlements use cloud resource names in a deprecated format. The following entitlements require migration: `<Entitlement Name>`. Please review the documentation on migrating resource names to the common JSON syntax. | Review the [Migrating DNS settings](/v1/docs/migrating-dns-settings-v7-0) documentation. | | Controller | Warning | Some entitlements use deprecated host formats (the "domain://" prefix, the "dns://" prefix with glob syntax or bare hostnames containing glob syntax). The following entitlements require migration: `<Entitlement Name>`. Please review the documentation on migrating to the dnsfwd:// format. | Review the [Migrating DNS settings](/v1/docs/migrating-dns-settings-v7-0) documentation. | | Controller | Warning | Trusted Network Detection settings are defined in more than one active policy for a user. The setting from policy `<Policy name>` is being used because it comes first alphabetically. | One or more users have a conflicting Trusted Network Detection setting across their policies. This most commonly occurs in device policies or the device section of mixed policies. Identify which user has `<Policy name>` assigned, go to their session details, and run ***Analyze Policy Assignments***. This shows which items are conflicting. Update the access criteria to resolve the conflict. | | Gateway | Warning | Brokered entitlement `<entitlement name>` host `<hostname>` resolved to `<# of IP addresses>` IPs; only the first 10 are shown as app shortcuts. | When a brokered SSH or RDP entitlement host resolves to more than 10 IPs, the session caps the per-IP shortcut at 10. The remaining IPs are dropped. | | Gateway | Warning | Failed to evaluate condition `<Condition Name>`. It timed out after X seconds. | Review the condition and determine why it is not evaluating within the time limit. Go to the specific condition and test it with an active user to confirm whether it executes in time. | | Gateway | Warning | `<Resolver name>` the assets filter `"<filter>"` matched `<N>` assets which carry no ipv4 and no ipv6 and therefore resolve to nothing. See the cz-gonamed journal for which those assets are. | Review the cz-gonamed journal entry for the affected assets. | | Gateway | Warning | The client with DN: `<Client DN>` is showing abnormal high signalling towards the Gateway, and has been loadlimited, until: `<time>` | The client DN has repeatedly retried connections to the same Gateway and has been load-limited. Review the client logs for `<Client DN>` and search the driver logs to determine why the client is retrying connections to this Gateway. | | Gateway | Warning | The following hostnames have been unresolved for at least X seconds | One or more hostnames could not be resolved by the DNS server specified in the DNS name resolver. Review the listed hostnames and confirm that the DNS configuration is correct. | | ZTP | Error | Failed to communicate with Risk Engine. | One of the Controllers could not reach the ZTP service. Confirm that all Controllers can reach the ZTP service. | | ZTP | Warning | Risk Engine is not active because this Collective is not registered to ZTP. | Confirm that the Collective is registered to ZTP. | | ZTP | Warning | Risk Engine is not available. | A network configuration issue exists — for example, a firewall is blocking the Controller from connecting to ZTP, or the ZTP services are down or experiencing technical issues. | | ZTP | Warning | Risk Engine live alerts not available. Socket connection is not established. | A network configuration issue exists — for example, a firewall is blocking the Controller from connecting to ZTP, or the ZTP services are down or experiencing technical issues. Check the status of your socket connection. | | ZTP | Error | ZTP registration has been revoked. Contact your ZTP administrator for more details. | The ZTP account is no longer valid. Contact your ZTP administrator to obtain valid credentials. |