Why would SSL inspection fail for one site on one Fortinet firewall?

November 16, 2026 5 answers
Asked by Vessik.8d

A customer cannot reach one website through their Fortinet firewall. The security log says it cannot retrieve the server certificate. Other HTTPS sites work, and the site works from our office through a similar firewall on the same firmware.

A higher-priority rule that skips SSL inspection lets the site load, but it also means losing some filtering. What would you check before relying on that workaround?

Answers

p.847+fusepocket

Start by comparing the actual inspection profiles and policy settings, not just the firmware versions. Same hardware and firmware do not guarantee the same configuration.

Check the certificate probe failure setting in particular. Firmware defaults can differ by version, and allowing traffic when a probe fails may restore access without fixing the reason the certificate could not be retrieved. Treat that as a security tradeoff, not a diagnosis.

Vessik.8d:

If the probe fails but traffic is allowed, would the browser still check the certificate?

q.490!parcelwheel:

The browser normally validates the certificate it receives, but that does not replace whatever inspection the firewall could not perform. Check the behavior of the specific profile and firmware before changing the setting.

Reply to this answer
u.756+drumcase

Get a packet capture on both sides of the firewall while reproducing the failure, and compare it with a successful connection. Look at the TLS handshake and where it stops. A verbose curl test and an OpenSSL connection using the hostname can add useful detail too.

Connecting directly to an IP is not a clean equivalent test. The server may select a different certificate or site when the hostname is missing. Ping working only tells you the address responds to ping, not that the TLS exchange is healthy.

Reply to this answer
_t47!valvecrayon.3

I'd look at DNS next. Compare what the client and the firewall resolve for the affected hostname, then compare those results with the office. Different answers could send the certificate probe and the client to different endpoints, so same firewall model does not necessarily mean the same connection.

Reply to this answer
_f29+drainquill.6

Check the certificate chain and the firewall's trusted CA store too. The browser and firewall can have different trust stores, and a matching leaf certificate alone does not prove the firewall can build and validate the chain.

Compare the chain presented on each path and investigate missing intermediates or trust differences before importing a CA certificate. Only add a CA you have independently verified and intend to trust.

Reply to this answer
Rilvo-3x

Another possibility is an MTU or path fragmentation problem. A TLS handshake can fail even when ping and simpler connections work. If the capture shows larger handshake packets going missing or repeated retransmissions, investigate path MTU discovery and test an MSS adjustment rather than changing it blindly.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions