I'm having an oddball issue with HTTP/HTTPS traffic through my FG-100A running 4 MR3 Patch 18. The basic architecture is Internet<->Modem<->FG-100A<->Switch+WAP<->Clients. The switch is wired into the "internal" port of the FG-100A (physically into port 1). The 100A's "dmz1" port is connected to a WAP. 95% of the time everything works perfectly. The rest of the time, sporadically and without any notice (that I'm aware of), all web traffic (HTTP/HTTPS) to LAN stops working. Below are my observations:

  • DNS/PING/SNMP still works - I can resolve and ping IPs both locally (private IP space) as well as globally on the Internet (e.g. or google.com)
  • FG100A's administrative interface becomes inaccessible (SSH/Telnet too), but SNMP/PING seems to continue to work just fine
  • SNMP shows that my CPU is far below 20% and memory is sitting at around 40-50%
  • IPSec tunnels still working (but haven't checked web traffic through the tunnel)
  • Number of connections/sec is <10/s and total connections is <1000
  • Logs show nothing out of the ordinary - usual messages from when my system is working normally
  • Seems to happen randomly and isn't triggered by any specific site or class of sites
  • I'm not using any IPS/Web Filter/AV or other UTM features, i.e. no policy has UTM enabled
  • SSL-VPN clients can VPN in from remote sites and are able to connect to the Internet and browse normally!
  • curl http://x.y.z.com works just fine - even when this issue is active
  • curl http://x.y.z.com/blah.blah.html will just hang until the connection times out or is reset by peer (normally the first)
  • All LAN clients are always accessible fully
  • Issue happens any time of day, but once it happens, is likely to recur in quick succession for the next several hours up to a day
    • Once "resolved", it will generally not recur for several days, sometimes nearly 2 weeks
  • The modem remains accessible and is working through all of this (tested by directly connecting a client to the modem during an outage)
  • Clients on the WAP connected to the "dmz1" port are unaffected
  • No policy or dynamic routes (only statics)

I've tried a few things over the span of a couple of months to try to get to the root of the problem: - I disabled all UTM (AV/IPS/DoS) references from my policies - Moved switch<->FG-100A uplink from port 1/internal to port 2/internal - Tried running traces to identify the issue via SSH, but SSH drops when the issue kicks up

The only solution I have to this right now is a reboot, either via a physical power cycle, or accessing the administrative interface via SSL-VPN for a CLI/GUI reboot. I don't have a console cable, so that's my next step - wire the console into a client and take a look when things go awry next.

Has anyone run into such an issue or have any insights given some of the parameters above? Based on the curl tests, it looks like the Fortigate is proxying HTTP connections and perhaps that proxy process has a software defect? Reaching here...

edit 1:

Some more debugging seems to show that curl always seems to work with "simple" web pages, i.e. text-only pages with no HTML formatting. A simple HTML web page with an included embed (Flash) wouldn't work when this problem occurs. I haven't tried a straight HTML page yet. I'm suspecting some sort of IPS/AV is still active despite my setup not having them enabled. I think I've gone through all the nooks and crannies of the config, but if anyone knows of a definitive, perhaps CLI based way, of debugging the status of the UTM system, I'd certainly appreciate a pointer.

  • I ran into something with a Fortigate appliance once. I believe the appliance had to be installed inline. Get ahold to Fortigate technical support. They should be able to help you. Start by verifying that the thing is plugged in correctly (inline vs some type of WCCP/SPAN/reditect or something). May 11, 2015 at 2:38
  • @RonRoyston: Could you elaborate on what you mean by inline? I'm not using proxy based inspection for any traffic (the default profile is actually set to flow based - but I've tried both). Also, unfortunately, we don't have a support contract for the FG100A (too old?). May 11, 2015 at 6:47
  • All http/s traffic. So webpages don't open in the browser but pings work. Could this be an issue with the switch?
    – allwynmasc
    May 23, 2015 at 8:26
  • @allwynmasc I don't believe it is a switch issue for two reasons: 1) I have tried another switch - no good comes of it. 2) When this issue manifests, I can still access local resources remotely via VPN. May 25, 2015 at 23:42
  • I now a similar issue like this. The FGT GUI is not accessible through any of the client machines except 1 i guess. The FGT can be pinged though and debugs show the request coming through but the page doesn't load.
    – allwynmasc
    Sep 29, 2015 at 9:10

2 Answers 2


I was never able to solve this issue. It seemed to be something within the FGT kernel and without an active Fortinet subscription, my working "solution" was to upgrade to an FGT-110C running 5.2.x.


I had this exact issue. I beat my head against a wall for hours before the Fortigate support tech suggested disabling my Antivirus. That was it. I still don't understand why my Cisco Anyconnect didn't have any issue with this, but the Forticlient did.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.