Skip to main content
yangw
Staff
Staff
Oct 6, 2026 7:02 AM UTC

Troubleshooting Tips: Admin is logged out of the GUI immediately after login (login must be entered twice) on FortiGate version 7.6.7

  • Oct 9, 2026 11:11 AM UTC
  • 1 reply
  • 831 views
  • Translate All

Description

This article describes an issue on FortiOS version 7.6.7: some administrators are kicked back to the login page right after a successful GUI login; it is necessary to enter credentials a second time before the dashboard loads.

In other cases, the first attempt shows a blank/white page, and a later attempt loads normally. The login may be recorded in the event log together with an HTTPS connection error, even though authentication itself succeeds.

Scope

FortiOS version 7.6.7.

Solution

Symptoms:

After entering the username and password, the login page reappears instead of the dashboard. Entering the credentials a second time succeeds and the GUI loads.


The issue affects GUI (HTTPS) logins only, SSH sessions are not affected. It may be seen across Chrome, Edge, and Firefox, and sometimes in /private mode as well.


An 'HTTPS connection error' may be logged in the event log.


Root cause:

When signing in through a web browser, the page loads a large number of small resources all at once (far more than in earlier releases). The web interface's activity monitor mistakes this normal burst of activity for a brief attack and interrupts the login, dropping back to the login page, even though the username and password were already accepted.


This is why the login can appear in the event log as successful while the page still sends back: authentication succeeds, but the session is cut before the dashboard finishes loading.

Related known issues in the 7.6.7 release notes:


Resolution:

Fixed in FortiOS version 7.6.8 (and above version 8.0.1).
The fix scopes the unauthenticated request-body monitor to body-carrying methods only, raises the unauthenticated request timeout from 1 s to 10 s, and reworks the rate-limiter token pricing and refund logic so a normal GUI bootstrap is not mistaken for an attack and killed.


Upgrade to FortiOS version 7.6.8 or above to resolve the issue.


Workaround (until upgrade):

Until the upgrade can be performed, one of the following avoids the problem:

  • Clear the browser cache and cookies associated with the FortiGate, then log in again.

  • Access the GUI in the browser's Incognito/InPrivate mode.

  • Simply log in a second time; the second attempt loads the dashboard normally.


Diagnostic Commands:

Useful while reproducing the issue:


diagnose debug reset


diagnose debug console timestamp enable


diagnose debug application httpsd -1


diagnose debug application node -1


diagnose debug application http_authd -1   # or http_auth


diagnose debug enable


Stop with:

diagnose debug disable
diagnose debug reset

    1 reply

    New Member
    Oct 29, 2026 5:10 PM UTC

    I find it funny that 7.6.8 version is listed as fixed applied, yet I just upgraded to that version and two of my fortigate locations are having similar problem. Yet in this case the issue is both with GUI (443) and SSH. Yet, I can access the firewall using a dedicated management interface via both connections. I will open a ticket shortly for this instance.                    

                          LAN      MGMT 
    TCP connectivity            YES                YES
    SSH listener                YES                YES
    SSH negotiation             starts             works
    SSH session                 RESET              works
    HTTPS listener              YES                YES
    HTTPS/TLS exchange          starts             works
    HTTPS session               RESET              works

    Translate
    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024