UPDATE 16.30 CET: Cloudflare has resolved the issue. All workarounds can now be disabled, as they are no longer needed. The root cause has not yet been published. ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
In a significant move by Fortinet, the upcoming FortiOS version 7.4.4 introduces a pivotal change affecting numerous FortiGate devices. Users planning to upgrade need to be aware of the substantial shift from proxy-based features, which will no longer be supported under this new firmware version.
Traffic can be UTM inspected on the FortiGate either flow-based or proxy-based. Both inspection modes have advantages and disadvantages. Therefore it is very important to use the right inspection mode for the concerning purpose.
On Mai 2021, Let’s Encrypt issued a note about the expiration of their DST Root CA X3:https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ Now that this root certificate has expired (2021-09-30), your systems might issue a warning when connecting to sites using Let’s Encrypt certificates. To fix this glitch on a general client, follow the instructions…
On some FortiGate models, you are being asked to connect a self-loopback cable on some ports during the HQIP test. This request looks like the following CLI output:
Since June 1st you may notice that some websites (https) are not working anymore when Fortigate or the Palo Alto Networks Firewall is doing decryption or certificate inspection. Typically you are getting one of the following error messages:
