Description |
This article describes how to resolve the captive portal issues affecting FortiAuthenticator v6.6.3 GA. |
Scope | FortiAuthenticator v6.6.3 GA. |
Solution |
A working captive portal setup in 6.6.2 GA and older might break with the upgrade to v6.6.3 GA. The error given to the end user is: 'Please enter correct credentials.'. The FortiAuthenticator admin will find the following corresponding errors.
Log example:
Authentication failed, NAS is not allowed for authentication
RADIUS debug example:
(0) facauth: ERROR: Invalid client_address format: fortigate.local
The requirement for this to continue working is to upgrade to the special built or to at least v6.6.4 GA and:
Or:
For example:
> exe nslookup fortigate.local Name: fortigate.local
An upgrade alone to v6.6.4 GA or higher will not fix this issue. One of the aforementioned requirements must also be met.
Note: If the portal still does not work after upgrading to v6.6.4, the admin checks the logs and finds the message 'Error resolving FQDN: fortigate.local-Validation result: no match'. This error occurs when the FQDN cannot be resolved to an IP address. To avoid this error, the configured DNS on FortiAuthenticator must be able to resolve the FQDN to an IP address.
AZR-FAC-01 radiusd[11792]: (5327) facauth: WARNING: Failed to resolve FQDN: fortigate.local, do matching as it is.
This error occurs when the FQDN cannot be resolved to an IP address. To avoid this error, the configured DNS on FortiAuthenticator must be able to resolve the FQDN to an IP address. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.