Read the SSL VPN failure log, match the reason to the causes Fortinet documents, run the right debug, and tell a user problem from password guessing.
Jump to the causessslvpn_login_permission_denied is the reason FortiGate writes in a failed SSL VPN login event (log ID 0101039426, action="ssl-login-fail"). It means FortiGate rejected the login. Fortinet documents it for a wrong password, a failed LDAP group match, and RADIUS or LDAP setups that deny an authenticated user. Read it with the username and source IP.
sslvpn_login_unknown_user is different: FortiGate could not match the submitted name to any user it is allowed to authenticate.
Every SSL VPN login failure uses the same event and message. The reason field is what changes.
This example follows the log Fortinet publishes in its tunnel-type technical tip. The address and username are placeholders.
logid="0101039426" type="event" subtype="vpn" level="alert"
logdesc="SSL VPN login fail" action="ssl-login-fail"
tunneltype="ssl-web" remip=192.0.2.44 user="example-user"
group="N/A" reason="sslvpn_login_permission_denied"
msg="SSL user failed to logged in"
msg="SSL user failed to logged in" is the same text for every failure. It does not tell you the cause.reason narrows the cause: sslvpn_login_permission_denied, sslvpn_login_unknown_user, or sslvpn_login_password_expired for an expired local password.remip is the source address and user is the name that was typed.tunneltype="ssl-web" on a FortiClient failure is normal. Fortinet explains that the client first reaches the HTTPS login page, so a failed login is logged as web mode.In the GUI, open Log & Report > System Events, select VPN Events, and filter for action ssl-login-fail. FortiOS 7.0 uses Log & Report > Events. From the CLI:
execute log filter category event
execute log filter field subtype vpn
execute log filter field action ssl-login-fail
execute log display
The full field reference is in FortiGate SSL VPN log messages and FortiClient error codes.
The same reason covers a wrong credential and several authorization problems. FortiClient usually shows “Permission denied. (-455)”.
| Cause | What you see | Fix |
|---|---|---|
| Wrong password | The sslvpn debug shows login_failed ... failed [sslvpn_login_permission_denied] for that user. |
Confirm the password. If the user is sure it is right, check the causes below. |
| LDAP group does not match the FortiGate group | The fnbamd debug ends with find_matched_usr_grps-Failed group matching. In Fortinet’s example, LDAP returned the group under one OU and the FortiGate group was set to another. |
Set the group match on FortiGate to the group DN that the debug shows LDAP returning. The group must be used in the SSL VPN settings and in the SSL VPN firewall policy. |
| LDAP user logs in with an email address | Fortinet’s example shows failed [sslvpn_login_permission_denied] for a name in email form, where the LDAP setup expected the plain username. |
Log in with the username format the LDAP server object is set to match, and confirm the user is in the LDAP group. |
| RADIUS does not send the tunnel IP | With set ip-mode user-group, the debug says the login requires RADIUS to provide a tunnel IP. Credentials are correct but the login is denied. |
Return a correct Framed-IP-Address from the RADIUS server, or set the portal to ip-mode range with a local address pool. |
| Password guessing | Fortinet’s article on frequent SSL VPN failed-login alerts from unknown public addresses shows ssl-login-fail events with this reason. |
See real user or brute force below. |
FortiGate could not find the submitted name among the users it may authenticate for this login.
sslvpn_login_unknown_user. Fortinet suggests typing the exact name or making local usernames all lower case.VPN-Users is not vpn-users).remoteauthtimeout under config system global).Many sslvpn_login_unknown_user events with names nobody in your organization uses are a common sign of automated guessing. Fortinet describes this pattern as “a lot of unknown failed login attempts from unknown IP addresses or countries.”
Reproduce one failed login with debug running. The sslvpn debug shows the reason; fnbamd shows authentication and group matching.
diagnose debug reset
diagnose debug console timestamp enable
diagnose debug application sslvpn -1
diagnose debug application fnbamd -1
diagnose debug enable
Ask the user to try once. On a busy gateway, other users’ logins appear too, so match the username and timestamp.
Fortinet’s examples show lines such as login_failed:405 user[guest],auth_type=1 failed [sslvpn_login_permission_denied] and login_failed:494 user[...],auth_type=1 failed [sslvpn_login_unknown_user]. A realm line such as validating with SSL VPN authentication rules (1), realm () shows which realm was used; empty brackets mean none.
In the fnbamd output, Failed group matching means the remote server answered but the user’s groups did not match the FortiGate group.
diagnose test authserver ldap <ldap-server-name> <username> <password>
This tests authentication against the LDAP server object outside the VPN. Compare the groups it returns with the group configured on FortiGate.
diagnose debug disable
diagnose debug reset
Neither reason proves an attack. The pattern across many events does.
| Pattern in VPN Events | More likely | Next step |
|---|---|---|
| One real username, a few failures, from an address the user normally connects from | User or configuration problem | Run the debug above for that user. |
| Many different usernames, including names you do not use (such as admin or test), from one address | Automated guessing | Block the source; check whether the address is on a known-attacker list. |
| Many usernames or one real username from many addresses, a few attempts each | Distributed password spraying, which stays under a per-IP limit | MFA, source restrictions, and blocking known sources. See VPN password spraying. |
| Real users locked out at the directory while FortiGate shows failures for their names | Guessing against real accounts reaching LDAP or RADIUS | Fortinet documents SSL VPN realms to keep arbitrary logins away from the remote server. See account lockout prevention. |
Before you block an address, confirm it is not a shared office or partner egress address that real users connect from. FortiGate’s own per-IP limit (login-attempt-limit, default 2, with login-block-time, default 60 seconds) blocks repeat attempts from one address for a short time; the limits, reset commands and “too many bad login attempts” message are covered in FortiGate SSL VPN failed login attempts.
Fixing a user’s group mapping does not stop the guessing. Fortinet’s brute-force resource list includes blocking listed IPs with a threat feed.
ThreatListPro is a plain-text IPv4 feed that a FortiGate loads as an IP Address threat feed and denies in a local-in or firewall policy. It covers 5.4M+ IPv4 addresses, is checked for new attackers every 6 hours, and comes from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. Setup is in the FortiGate threat feed setup guide and the FortiGate SSL VPN brute force guide.
Test with the free 200-entry sample first. No signup is required.
It is the reason value in a failed SSL VPN login event (log ID 0101039426, action ssl-login-fail). FortiGate rejected the login. Fortinet documents it for a wrong password, a failed LDAP group match, an LDAP login typed as an email address, and a RADIUS server that does not return the tunnel IP when ip-mode user-group is set.
FortiGate could not match the submitted name to a user it is allowed to authenticate. Fortinet lists a user that is not configured, a typo, a local username typed in the wrong case, a missing or wrong realm, a user or group missing from the SSL VPN firewall policy, an authentication rule on a different source interface, and LDAP or RADIUS problems.
It is the msg text of FortiGate's SSL VPN login-failure event, log ID 0101039426 with action ssl-login-fail. The wording is the same for every failure, so read the reason field (for example sslvpn_login_permission_denied or sslvpn_login_unknown_user), the user and the remip source address to find the cause.
Not by itself. A real user with a wrong password or a group problem produces the same reason. Fortinet's own brute-force example shows this reason in its logs. Many different usernames, names your organization does not use, or repeated failures from addresses your users never connect from point to automated password guessing.
Run diagnose debug reset, diagnose debug console timestamp enable, diagnose debug application sslvpn -1, diagnose debug application fnbamd -1 and diagnose debug enable, then reproduce one login. The login_failed line shows the reason, and fnbamd shows group matching. For LDAP, diagnose test authserver ldap tests one user. Run diagnose debug disable when done.
Authentication can succeed while authorization fails. Fortinet documents an LDAP group that does not match the FortiGate group because the returned OU differs, a user not allowed in the SSL VPN policy, an email address entered where the LDAP setup expects a plain username, and a RADIUS server that does not send Framed-IP-Address when ip-mode user-group is set.
ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed. Yearly is $200. Enterprise is $99.99/month for up to 50 firewalls. Paid plans have a 14-day money-back guarantee.
Start a 14-day free trial Or test 200 entries first: free, no signupLockout timers, the full log reference, and the feed setup.