Console access and certificates
This page covers how administrators reach the Airgate console securely: the HTTPS certificate browsers see, optional publishing through Cloudflare Tunnel, how sign-in works, and how to recover when the only platform administrator is locked out. It is for platform administrators of an appliance or a self-hosted deployment.
The console HTTPS certificate
Section titled “The console HTTPS certificate”Airgate serves the console, the REST API, the guest and BYOD portals and the site connector API over HTTPS with one certificate: the Console HTTPS certificate. It is managed in Certificates › Server certificates, in the Console section at the top.
| Source | Behaviour |
|---|---|
| Generated (default) | Issued by the appliance’s own root certificate authority. On first use it is named after the host of the Console address (localhost when the console address is an IP address). Airgate renews it automatically 30 days before it expires |
| Uploaded | A certificate from a public or enterprise CA. Never renewed automatically: replace it before it expires |
A new certificate is used from the next HTTPS connection; no restart is needed. With several nacd replicas, the others pick it up within a minute. Only platform administrators can change it. The listener accepts TLS 1.2 and later.
Use a certificate from a public or enterprise CA (recommended)
Section titled “Use a certificate from a public or enterprise CA (recommended)”- Get a certificate for the console’s name (for example
nac.contoso.com) from your CA, with its private key and the intermediate chain, in PEM format. - Go to Certificates › Server certificates › Console HTTPS certificate and select Upload custom.
- Paste or load the certificate, the private key (Load key file) and the chain (Chain (optional) / Load chain file).
- Select Upload & activate.
Browsers and site connectors then trust the console without extra steps.
Keep a generated certificate
Section titled “Keep a generated certificate”- To add names (for example a second DNS name), select Regenerate on the Console HTTPS certificate and enter the names.
- Make browsers trust it: download the root from Certificates › Certificate authorities and install it as a trusted root certification authority on administrators’ computers (Group Policy, Intune or your device management).
- Site connectors on your own Linux hosts need the same root:
nac-edge enroll --api-ca <root.pem>.
Publish the console through Cloudflare Tunnel
Section titled “Publish the console through Cloudflare Tunnel”On a self-hosted deployment you can publish Airgate’s HTTPS services (console, API, portals, site connector API) through a Cloudflare Tunnel instead of opening an inbound port. RADIUS, RadSec and TACACS+ are not HTTP; they keep their own ports.
The deployment includes two optional tunnel services:
| Service | Use |
|---|---|
tunnel (profile public) |
A named tunnel from your Cloudflare Zero Trust account, for production |
tunnel-quick (profile quick) |
A temporary *.trycloudflare.com address, for a short demo only |
Set up a named tunnel
Section titled “Set up a named tunnel”-
In Cloudflare Zero Trust, go to Networks › Tunnels and create a tunnel. Add a public hostname, for example
nac.contoso.com, whose service is nacd’s plain HTTP listener inside the deployment,http://nacd:8090. -
Copy the tunnel token.
-
Set the console address to the tunnel’s hostname: on the appliance run
sudo airgate-setupand enterhttps://nac.contoso.comas the Console address. -
Add the token to the deployment settings as
CLOUDFLARE_TUNNEL_TOKEN(on the appliance,/opt/airgate/deploy/.env, as root). -
Start the tunnel:
Terminal window sudo airgate-compose --profile public up -d tunnelThe tunnel image is downloaded from the internet the first time, so the host needs outbound internet access.
For a demo, sudo airgate-compose --profile quick up -d tunnel-quick starts a temporary tunnel; its *.trycloudflare.com address is in sudo airgate-compose logs tunnel-quick.
Client addresses behind a proxy
Section titled “Client addresses behind a proxy”nacd trusts forwarding headers (CF-Connecting-IP, X-Forwarded-For, X-Forwarded-Proto) only from the addresses in TRUSTED_PROXIES, which by default are exactly the two tunnel services. Requests through the tunnel then show the real client address in the audit log, the Sign-in log and per-address limits, and portals know the request arrived over HTTPS. The same headers from any other sender are ignored, so a client cannot choose the address that gets logged. If you put Airgate behind another reverse proxy, add its address to TRUSTED_PROXIES (IP addresses or CIDR ranges, comma-separated).
A reverse proxy in front of Airgate must also pass Connection: Upgrade and Upgrade headers for /edge/v1/tacacs and allow reads of at least 60 seconds, so site connectors can tunnel TACACS+ and long-poll for jobs.
Sign in to the console
Section titled “Sign in to the console”- Administrators sign in with their email and password. When exactly one administrator’s email starts with a name, that name alone also works (
aliceforalice@contoso.com); an exact email always wins, and an ambiguous name is refused like a wrong password. - After 10 failed attempts an account is locked for 15 minutes after the last failure. The email and the short name share one lockout.
- A console session lasts 8 hours.
- With console single sign-on, administrators sign in through your identity provider (Microsoft Entra ID, Okta, Google and other SAML 2.0 or OpenID Connect providers), which also applies your MFA and conditional access. Password sign-in keeps working next to it.
Reset a platform administrator password
Section titled “Reset a platform administrator password”If the only platform administrator has lost the password or locked the account, reset it from the appliance’s shell. Sign in on the VM console or over SSH as airgate:
sudo airgate-compose exec -e ADMIN_PASSWORD='<new password>' nacd nacd reset-admin-password- The new password must have at least 8 characters.
- With more than one platform administrator, name the account: add
--email admin@contoso.comat the end. - The account gets the new password, is enabled again, and every session it had is signed out.
- The reset is written to the audit log (action
password_reset, actorsystem).
A lockout from failed attempts still expires 15 minutes after the last failure.
Tenant administrators who forget their password are reset by another administrator of the tenant in Settings › Administrators, or by a platform administrator.