Skip to main content
3pointD
New Member
September 13, 2013
Question

Web Interface Not fully Loading

  • September 13, 2013
  • 3 replies
  • 6339 views
I' ve got an issue with a 20C where every week when I log into the web interface I get the header bar and page background of the interface but the interface is completely blank. I can log out successfully by the log out button in the header bar but that is it. Other than that the system seems to be running normally. I tried a restart from CLI but it hangs and I eventually have to unplug the unit to reset it and the web interface comes back. My question: Is it possible to restart the web server or something so I don' t need to physically go and unplug the firewall to get the web interface back? Also, any ideas why this may happen? This unit has been running fine from day one. The only thing I changed before the issue started is I added a site to site vpn (fortigate to fortigate) but the vpn is not currently enabled. Version: Fortigate-20C V4.0,build0511,120110 (MR3 Patch 4) Just looked at sys top and I see 11 instances of httpd running. None have overly high cpu or memory usage. I tried killing these but nothing changes. I tried to exec reload httpd but i get an error back, it looks like this isn' t the correct command. Any help would be greatly appreciated. Thanks!

    3 replies

    Dave_Hall
    New Member
    September 13, 2013
    Just looked at sys top and I see 11 instances of httpd running. None have overly high cpu or memory usage. I tried killing these but nothing changes. I tried to exec reload httpd but i get an error back, it looks like this isn' t the correct command. Any help would be greatly appreciated.
    How about rebooting the fgt? ;-) I strongly suggest moving to 4.0 M3 patch 14 (or patch 15) as this firmware is easier on the memory usage on the little guys. Also most of the earlier patch firmwares have memory leaks. (If you do upgrade, please follow the upgrade path as recommended by Fortinet.)
    3pointD
    3pointDAuthor
    New Member
    September 16, 2013
    Hi Dave, Thanks, I was trying to get around that since the unit is about 60 mi away. When it hits the state it' s in it won' t respond to a reboot command via ssh even though I can log in fine. Thanks for the info on the firmware. I will address that asap when I get control back.
    ede_pfau
    SuperUser
    SuperUser
    September 17, 2013
    In your case, you might consider a daily (nightly) auto-reboot:
    conf sys global     set daily ena     set restart 01:30  end
    3pointD
    3pointDAuthor
    New Member
    September 19, 2013
    Thanks, I will consider doing that. I appreciate the suggestions guys!