Description | This article describes an issue with SSL VPN users with FortiToken but NTP is not synchronized. |
Scope | FortiGate, FortiToken. |
Solution |
When a user is connected to an SSL VPN but gets this output: 'Credential or SSLVPN configuration is wrong. (-7200)'.
This assumes that all configurations are correct on the SSL VPN setting, group, and firewall policy:
Run debug on FortiGate for authentication via CLI:
diagnose debug enable FortiGate-VM64-KVM # [1937] handle_req-Rcvd auth_token req 539556049 for testuse r in
[2167] handle_req-Token check failed, result -30113
Verify if the NTPs are synchronized on FortiGate:
FortiGate-VM64-KVM # diagnose sys ntp status ipv4 server(192.168.168.1) 192.168.168.1 -- unreachable(0x0) S:7 T:535
After the NTP has been synchronized the SSL VPN connection with FortiToken should be connected. |
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.