Skip to main content
Debbie_FTNT
Staff & Editor
Staff & Editor
Oct 6, 2021 2:45 PM UTC

Troubleshooting Tip: FortiGate transparent web-proxy and certificate errors

  • Apr 16, 2026 12:51 PM UTC
  • 0 replies
  • 4969 views
  • Translate All

Description
This article expands upon the transparent web-proxy configuration guide:
https://docs.fortinet.com/document/fortigate/6.4.7/administration-guide/15908/transparent-proxy


Solution
FortiGates, when serving as transparent web-proxy, might still present their own certificates to the user during authentication if it happens over HTTPS, which can lead to certificate errors if the FortiGate certificates are not trusted.

This usually shows as warnings/errors in browsers regarding untrusted certificates or certificate issuers, such as this:



  
Certificates for proxy connections/captive portal are set in CLI here.
# config user setting
    set auth-cert <server certificate>
    set auth-ca-cert <CA certificate of server certificate>
end
Certificates for transparent (web) proxy in particular, however, are specified here:
# config web-proxy global
    set ssl-cert <server certificate>
    set ssl-ca-cert <server certificate>
    set proxy-fqdn <FQDN of FortiGate>
end
If a proxy-fqdn is defined here, the server certificate must contain the FQDN as subject and/or Subject Alternative Name.

Note:
There can be issues with Chrome or Chrome-based browsers not accepting the server certificate if it lacks a Subject Alternative Name (SAN).
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