Troubleshooting
This page lists common problems by symptom, with the exact diagnosis Monitor › Sign-in log shows and how to fix it. It is for administrators and help desk staff. For the tools themselves (trace, debug logging, packet capture), see Logs and debugging.
Start here
Section titled “Start here”- Find the sign-in in Monitor › Sign-in log: search for the user name or the device’s MAC address.
- No record at all: the request never reached Airgate, or Airgate ignored it. Go to Nothing in the Sign-in log.
- A refused record: the list shows a short diagnosis. Open the record: Summary explains why and shows How to fix; Trace shows each step; Computed attributes shows what Airgate knew about the user and device. Find the diagnosis below.
- Accepted, but the wrong access (wrong VLAN or role): open the record and check which access policy and rule matched in Summary and Trace. Reproduce it with Access › Test access for the same user, MAC address and network device.
Sign-in diagnoses
Section titled “Sign-in diagnoses”These are the titles the Sign-in log shows for a refused sign-in.
Accounts and passwords
Section titled “Accounts and passwords”| Diagnosis | Cause | Fix |
|---|---|---|
No account named “<user>” |
Airgate looked for the user in the directories this policy checks and did not find it | Check the user name for typos (for certificates: the UPN in the certificate). If the account lives in another directory, add that directory to the policy’s Check accounts in list. Repeated tries with names like admin or cisco usually come from someone logging in to the network device itself, or a device’s saved credentials: check that device’s management login settings |
| Wrong password | The user exists, but the password did not match | Ask the user to enter the password again; on the device, forget the Wi-Fi network to clear an old saved password |
| The account is disabled | The account is disabled in its directory | Enable the account if the user should have access |
| The account has expired | The account, or the guest’s access, has expired | Extend the account if access is still needed (Guests › Guest accounts › Extend) |
| Airgate couldn’t reach the directory | The directory did not answer, so the account could not be checked | Access › Directories › the directory › Test connection. Check the network path from Airgate (or the site connector) to the directory, the firewall, DNS and the bind credentials. For Microsoft Entra ID or Google, check the app registration’s secret has not expired |
Policy
Section titled “Policy”| Diagnosis | Cause | Fix |
|---|---|---|
| No access policy handles this sign-in | No access policy matches the request (network, connection type or switch / access point) | Add or widen an access policy for this Wi-Fi network or switch in Access › Access policies |
| The device used a sign-in method this network doesn’t allow | The device used, for example, PEAP where the policy allows only EAP-TLS | Fix the device’s Wi-Fi profile (for example certificate / EAP-TLS), or allow the method in the policy |
Denied: no rule of the policy allowed this device, or Denied: <check> check failed |
The sign-in itself worked, but no rule of the policy matched, so the default (deny) applied. The record lists each failed condition with the value Airgate saw and the value the rule needs | Compare the device with the policy’s rules and the Computed attributes tab. The fixes for common checks are below |
Common failed checks in a Denied diagnosis:
| Failed check | Shown value | Fix |
|---|---|---|
| Managed by Intune | not found in Intune (device MAC not in the Intune sync) |
Enroll the device in Intune, then select Sync now on Integrations › Microsoft Intune instead of waiting for the next sync |
| Managed by Intune | not found in Intune: the device uses a private Wi-Fi address and its certificate has no Intune device ID |
See Intune or SentinelOne not found because of private Wi-Fi addresses |
| Intune compliance | The device’s compliance state | Open the device in Intune and fix what makes it noncompliant; then Sync now |
| SentinelOne agent | not found in SentinelOne |
Install or re-register the SentinelOne agent; then Sync now on Integrations › SentinelOne |
| SentinelOne agent | not found in SentinelOne: the device uses a private Wi-Fi address … |
See private Wi-Fi addresses |
| SentinelOne threats | infected |
Resolve the threat in the SentinelOne console; then Sync now |
| Guest portal login | no portal login yet |
Normal first step for guests: the guest signs in on the guest portal first |
| Member of group | no groups found |
Add the user to the required group in the directory, or change the rule |
Certificates (EAP-TLS)
Section titled “Certificates (EAP-TLS)”| Diagnosis | Cause | Fix |
|---|---|---|
| The device’s certificate has expired | The device signed in with a certificate past its expiry date | Sync the device so Intune renews its Airgate certificate (on Windows: Settings › Accounts › Access work or school › Info › Sync). If it keeps the old certificate, delete it from the user’s personal certificate store and sync again |
| The device’s certificate is not valid yet | The certificate’s start date is in the future, usually because the device clock is wrong | Correct the device’s date, time and time zone, then reconnect |
| The device’s certificate was revoked | The certificate has been revoked in Airgate | If the device should have access, sync it so Intune issues a new certificate. If it was revoked on purpose (lost or retired device), no action is needed |
| The device’s certificate isn’t from a CA Airgate trusts | The device offered a certificate from another CA (the record shows the issuer); the network only accepts certificates issued by Airgate | Sync the device so Intune installs its Airgate certificate and the Wi-Fi profile that uses it. Enroll unmanaged devices. Remove old Wi-Fi profiles that still point at an old certificate |
| The device’s certificate was refused | The certificate could not be verified; the record gives the reason | Sync the device so Intune issues a fresh Airgate certificate, then reconnect |
| The device didn’t trust Airgate’s RADIUS certificate | The device ended the TLS handshake: it is missing Airgate’s root or intermediate CA, or its Wi-Fi profile expects a different server name | Make sure Intune has pushed the Airgate root and intermediate certificates (sync the device). Check the Wi-Fi profile’s trusted server name matches Airgate’s RADIUS certificate and the Airgate root is selected. On a personal device, trust the server certificate when prompted, or install the Airgate root CA |
| The secure connection with the device couldn’t be set up | Device and Airgate could not agree on TLS version or ciphers, or the device gave up half way | Update the device’s operating system and Wi-Fi driver; forget the network and connect again |
| The device stopped answering during sign-in | Airgate waited 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 the device. If it repeats, check that the Wi-Fi profile trusts the Airgate root and server name |
Any other refusal shows Sign-in refused with the technical reason; see the record’s Trace.
See Certificates and trust for how devices trust Airgate.
Intune or SentinelOne not found because of private Wi-Fi addresses
Section titled “Intune or SentinelOne not found because of private Wi-Fi addresses”Symptom: a managed, compliant device is denied with Managed by Intune or SentinelOne agent showing … the device uses a private Wi-Fi address and its certificate has no Intune device ID.
Cause: Windows, iOS, iPadOS, Android and macOS can use a random (“private”) MAC address per Wi-Fi network. Intune and SentinelOne report the device’s hardware MAC address, so Airgate cannot match the address the device signs in with. The device’s certificate does not carry its Intune device ID either, so Airgate has nothing else to match on.
Fix:
- In the Intune SCEP certificate profile for Airgate, add a Subject alternative name of type URI with the value
IntuneDeviceId://{{DeviceId}}. - Let devices receive the new certificate (sync them). Airgate then finds the device in Intune, and in SentinelOne, by its Intune device ID, whatever Wi-Fi address it uses.
- Until a device has the new certificate, turning off Private Wi-Fi address for this network on the device also works.
See Integrations › Microsoft Intune.
Nothing in the Sign-in log
Section titled “Nothing in the Sign-in log”| Check | How |
|---|---|
| Does the request reach Airgate? | Run a RADIUS packet capture (cloud, or the site connector) with the switch’s address in Only these hosts, and reconnect the device. No packets: the switch sends elsewhere, or a firewall drops UDP 1812 |
| Is the device known? | Packets arrive but no record: the source address or shared secret does not match Network › Switches and APs. Check Monitor › Alerts and events for Misconfigured Network Devices |
| Wrong shared secret? | In a capture, requests get no reply. Airgate reports wrong secrets for requests with a Message-Authenticator (all 802.1X and accounting) |
| Behind a site connector? | The device must be assigned to the connector, the connector Online, and the switch must send to the connector’s address, not Airgate’s |
| Device disabled, or assigned to a connector but sending directly? | Shown as a misconfigured device in Monitor › Alerts and events |
Network devices
Section titled “Network devices”| Symptom | Cause | Fix |
|---|---|---|
| Misconfigured Network Devices alert | Wrong shared secret, unknown source address, disabled device, or device assigned to a site connector but sending to Airgate directly | Open the event: it names the address and nearest known device. Fix the secret or the address in Network › Switches and APs |
| CoA (reauthenticate, disconnect) has no effect | The device does not accept CoA from Airgate: CoA not enabled, wrong port, or firewall blocks UDP 3799 | Turn on RADIUS CoA / Disconnect (RFC 5176) on the device in Airgate and configure Airgate (or the site connector) as a dynamic-authorization client on the device |
| A legacy device’s requests are dropped | It sends no Message-Authenticator while Require Message-Authenticator in Access-Requests is on | Update the device; turn the setting off for that device only if it cannot send it |
| TACACS+ logins to a switch fail | Wrong TACACS+ secret or no TACACS+ policy | Monitor › Admin login log; check the device’s TACACS+ shared secret |
Directories
Section titled “Directories”| Symptom | Cause | Fix |
|---|---|---|
| Airgate couldn’t reach the directory | Network path, DNS, firewall, TLS or credentials | Test connection on the directory; with debug logging on, Monitor › Logs shows the directory’s answer |
| PEAP-MSCHAPv2 fails for Active Directory users | Active Directory never gives out password hashes, so the check needs a domain-joined appliance or site connector | Join the appliance (Access › Directories › the directory › Domain join) or a site connector to the domain |
| Group-based rules never match | Groups not read, or rule uses a different group name or ID | Computed attributes shows the groups Airgate saw; Entra ID sends group object IDs unless configured otherwise |
Device sources (Intune, CrowdStrike, SentinelOne)
Section titled “Device sources (Intune, CrowdStrike, SentinelOne)”| Symptom | Cause | Fix |
|---|---|---|
| Device data missing or old | Sync failed or not run yet | Integrations › the source › Sync now; Monitor › Alerts and events shows failed syncs; Monitor › Logs (module extensions) shows the error |
| Managed device not found | Private Wi-Fi address | See above |
Site connectors
Section titled “Site connectors”See Install a site connector › Troubleshooting.
Appliance and console
Section titled “Appliance and console”| Symptom | Cause | Fix |
|---|---|---|
| Console does not open after a reboot | Services still starting, or a service failed | sudo airgate-compose ps; sudo airgate-compose logs nacd; sudo systemctl restart airgate |
GET /healthz answers 503 db_unavailable |
The database is not reachable | sudo airgate-compose ps postgres; check disk space with df -h |
| Browser certificate warning | Console certificate issued by the appliance’s own root | Use a public certificate or trust the root |
| Locked out of the console | Lost password or 10 failed attempts | Wait 15 minutes, or reset the platform administrator password |
| An update failed | See the update log | Software updates › If an update fails |
| A restore was refused | Backup newer than the installed version, or wrong passphrase | Backups and restore › Troubleshooting |
When you contact support
Section titled “When you contact support”Collect:
- the Sign-in log record (its ID, or a screenshot of Summary and Trace);
- Monitor › Logs with debug logging on while you reproduce the problem, saved with Download;
- a packet capture (
.pcap) if the request never arrives or EAP fails; - the Airgate version (Settings › Software update, or
sudo airgate-update status).
Do not send shared secrets, passwords or private keys.