Skip to content

Sign-in errors

When a sign-in fails, Monitor › Sign-in log shows an error code, the technical reason, and a plain-language diagnosis: what happened, why, and what to do. This page lists every diagnosis and every error code, so you can look one up or search the log for it (Error code filter).

  1. In Monitor › Sign-in log, set Result to Failed and find the request.
  2. The list shows a one-line summary, for example Wrong password or Denied by policy (a rule condition failed).
  3. Open the record. The Summary tab shows the diagnosis title, why it happened, what to do, and the facts Airgate checked (for example the certificate, its issuer, or the rule condition that failed with the device’s actual value).
  4. Computed attributes shows every attribute the rules saw; Trace shows each step of the decision; Input and Output show the RADIUS request and reply.

Airgate derives the diagnosis from the error code, the technical reason, the request and the trace. The Code column is the stable key of the diagnosis.

Code Title Cause Fix
client_cert_expired The device’s certificate has expired The certificate is past its expiry date. Sync the device so the MDM renews its certificate. If it keeps the old one, delete it from the user’s personal certificate store and sync again.
client_cert_not_yet_valid The device’s certificate is not valid yet The certificate’s start date is in the future, usually a wrong device clock. Correct the device’s date, time and time zone, then reconnect.
client_cert_revoked The device’s certificate was revoked The certificate was revoked in Airgate. If the device should have access, have the MDM issue a new certificate. If it was revoked on purpose (lost or retired device), no action is needed.
client_cert_untrusted The device’s certificate isn’t from a CA Airgate trusts The certificate was issued by a CA the tenant does not trust for Wi-Fi client certificates (the record shows the issuer). Install the Airgate-issued certificate and Wi-Fi profile through the MDM, enrol unmanaged devices, and remove old Wi-Fi profiles that point at another certificate. To accept another CA, import it under Certificates › Trusted CAs for Wi-Fi client certificates.
client_cert_invalid The device’s certificate was refused Another certificate problem (code 215), for example a failed status lookup, a certificate comparison mismatch, or a TLS session resumed through another tenant’s network device. Read the technical reason. Usually: have the MDM issue a fresh certificate, then reconnect.
Code Title Cause Fix
server_cert_rejected The device didn’t trust Airgate’s RADIUS certificate The device ended the TLS handshake (code 9020): it is missing the Airgate root or intermediate CA, or its Wi-Fi profile expects another server name. Push the Airgate root CA to the device. Check that the Wi-Fi profile’s trusted server name matches Airgate’s RADIUS server certificate and that the Airgate root is selected. On a personal device, accept the server certificate when asked.
tls_failed The secure connection with the device couldn’t be set up The device and Airgate could not agree on a TLS version or ciphers, or the device gave up (code 9021). Update the device’s operating system and Wi-Fi driver. Forget the network and connect again.
Code Title Cause Fix
user_not_found No account named “…” The user is not in any directory under Check accounts in (code 201). For EAP-TLS, the name taken from the certificate is not in the directories. Check the user name (for certificates, the name in the certificate). If the account is in another directory, add it to the policy’s Check accounts in list. Repeated PAP attempts with names like admin usually come from someone logging in to the network device itself, or a device with saved credentials.
bad_password Wrong password The account exists but the password did not match (code 216). Re-enter the password. Forget the Wi-Fi network on the device to clear an old saved password.
account_disabled The account is disabled The account, or the device for MAC authentication, is disabled (code 202). Enable the account if the user should have access.
account_expired The account has expired The account or guest access has expired (code 203). Extend the account (Guests › Guest accounts › Extend for guests).
Code Title Cause Fix
no_policy No access policy handles this sign-in No access policy matches the network, connection type or network device (code 9001). Add or widen an access policy on Access › Access policies.
method_not_allowed The device used a sign-in method this network doesn’t allow The method is not in the policy’s Allowed methods (code 9002). Fix the device’s Wi-Fi profile, or allow the method in the policy.
directory_unreachable Airgate couldn’t reach the directory The directory did not answer (code 9003). Check Access › Directories › Test connection, the network path and the credentials.
policy_denied Denied: … check failed / Denied: no rule of the policy allowed this device Authentication worked, but the rules refused (code 206). The record lists each failed condition with the device’s actual value and what the rule needs. See the condition-specific fixes below.

For policy_denied, Airgate names the failed condition and suggests a fix:

Failed condition Shown as Fix
Endpoint:Intune Managed Managed by Intune: not found in Intune Open the device in Intune and fix it or enrol it, then select Sync now on Integrations › Microsoft Intune.
Endpoint:Intune Compliance State Intune compliance Fix what makes the device noncompliant in Intune, then Sync now.
Endpoint:SentinelOne System Found SentinelOne agent: not found in SentinelOne Install or re-register the SentinelOne agent, then Sync now on Integrations › SentinelOne.
Endpoint:SentinelOne Infected SentinelOne threats: infected Resolve the threat in SentinelOne, then Sync now.
Endpoint:Access_Valid_Till Guest portal login: no portal login yet The guest logs in on the guest portal first (the normal first step).
Authorization:<directory>:Groups Member of group Add the user to the group, or change the rule.
Connection:SSID Wi-Fi network Check the policy’s SSID.
Endpoint:Status Device status Mark the device Known or change the rule.
Intune or SentinelOne condition, device on a private Wi-Fi address the device uses a private Wi-Fi address and its certificate has no Intune device ID Add the URI IntuneDeviceId://{{DeviceId}} to the Intune SCEP profile’s subject alternative name. Until the device has the new certificate, turning Private Wi-Fi address off for this network also works.
Code Title Cause Fix
device_stopped The device stopped answering during sign-in Airgate was waiting for the device, which never finished: usually the user cancelled a certificate prompt, the device does not trust Airgate’s server certificate, or it roamed away. Reconnect. If it repeats, check that the Wi-Fi profile trusts the Airgate root CA and server name.
other Sign-in refused Anything else. Read the technical reason.
Code Name in the log Written when
0 Success The request was accepted.
201 User not found No directory has the user or device, or the policy has no directory to check.
202 User account disabled The account or the device (MAC authentication) is disabled.
203 User account expired The account, guest access or MAC-authentication validity has expired.
206 Access denied by policy The rules denied (a Deny rule or default, or a profile with action Reject or Drop).
215 Client certificate invalid A client certificate problem: missing, revoked, expired, untrusted, status lookup failed, comparison failed, or a TLS session resumed without this tenant’s binding.
216 User authentication failed Wrong password, or a credential check failed without a more specific reason.
9001 No service matched No access policy matched the request.
9002 Authentication method not allowed The outer or inner method is not allowed by the policy, MAC authentication is not allowed, or the request carried no usable credentials.
9003 Authentication source unavailable A directory could not be reached and no later directory had the user.
9020 Device rejected the server certificate The device sent a TLS alert during PEAP, EAP-TTLS or EAP-TLS: it did not accept Airgate’s RADIUS server certificate.
9021 TLS handshake failed A PEAP, TTLS or FAST tunnel could not be set up for another reason.
9999 Internal error Airgate could not complete the request (for example a policy evaluation failure).

Session restrictions (SESSION enforcement profiles) use these codes for the checks they enforce on Monitor › Connected now:

Code Name
228 User exceeded bandwidth limit
229 User exceeded session duration limit
230 User exceeded session count limit

The Sign-in log also shows a name for these codes when a record carries one:

Code Name
101 Failed to perform service classification
102 Failed to perform policy evaluation
105 Internal error in performing authentication
106 Internal error in RADIUS server
204 Failed to classify request to service
205 AuthSource not configured for service
207 Failed to get client macAddress to perform webauth
208 No response from home server
209 No password in request
210 Unknown CA in client certificate
211 Client certificate not valid
212 Client certificate has expired
213 Certificate comparison failed
214 No certificate in authentication source
218 Authentication source timed out
221 Authentication source error
223 Username not available in request
224 CallingStationID not available in request
225 User account disabled
226 User account expired or not active yet
227 User account needs approval
6203 Command not allowed
9015 Client does not support configured EAP methods
9017 Failed to contact OCSP server

Some problems produce no Sign-in log record, because Airgate cannot tell which tenant or network device the request belongs to:

Problem Where it shows
RADIUS from an address that is not a network device Monitor › Alerts and events, category Network device
RADIUS or TACACS+ with a wrong shared secret Monitor › Alerts and events (for 802.1X and accounting, which carry a Message-Authenticator). A wrong secret on a PAP request without Message-Authenticator looks like a wrong password.
A disabled network device, or one assigned to a site connector but sending to the cloud Monitor › Alerts and events
Packets that never reach Airgate Monitor › Packet capture
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security