Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
agardener
New Contributor

FortiOS 5.02 / FGT 60C

Hi, I am having issues with 5.02 with the web gui within fortiexplorer (usb) and web gui by IP. Varius fields seem to require mandatory values and I get regular error 500 internal server errors. These issues vary by browser and are not consistent, some features are OK in one browser but not in another! Is there a recommended Browser and version that solves these issues? am I the only one getting these issues - I can find no mention of them on this forum? thanks Andrew
14 REPLIES 14
ede_pfau
SuperUser
SuperUser

hi, and welcome to the forums. Ahem, there is, how do I put it...there are still some minor glitches with v5.00 firmware. You would have a perfectly healthy FGT if you downgraded to 4.3.12. With a 60C you are not bound to run v5 so I' d recommend downgrading. Usually this will clear your config, though.

Ede

"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
agardener
New Contributor

Hi, Thanks for the prompt answer. I am new to Fortigate, but not to firewalls in general so I am not surprised to hear of early release glitches! I am happy to downgrade and re enter my config - it is a relatively simple config so will no take long. I also noticed that in 5.02 the DHCP settings have moved to the interface and lost the ability to enter lease times and domain names without reverting to the CLI, so downgrading to 4.3.12 has other advantages! Cheers Andrew
Uwe_Sommerfeld
New Contributor

downgrading will not clear your config completely. however many settings may be mismatched so I suggest you do a reset to firmware defaults after the downgrade and start from scratch. It took me ages to find the issues on my downgraded config...
romanr
Valued Contributor

Downgrading from 5.0.2 to 4.3.12 isn' t supported but works much better, than you would expect! You will lose most of your UTM config and all parts which are new in OS5... But interface/routing/core wireless config and also policies (minus utm features..) will be retained!
Jordan_Thompson_FTNT

FortiExplorer uses an older version of IE which results in some errors on the FortiOS GUI. We are currently fixing the issues on FortiOS with the extra " mandatory fields" when viewing from FortiExplorer. Can you provide more information on the ' internal server error' you are seeing? Please enable the following debug in the CLI: * diagnose debug enable * diagnose debug app httpsd -1 * diagnose web-ui debug enable
CG_5766

found a slightly better work around. With the FG hooked up to your computer via USB cable, launch FortiExplorer. From there it should find the FG. In FortiExplorer Go to the top left and go to Tools drop down and do Web-Based from there and it will launch a browser for the interface rather than in the FortiExplorer window. With this method I have seen less issues (using IE9 and Firefox).
CorneJvV
New Contributor

Hello All

 

I have the same issue on a 100D.

I have used various browsers, and all give me the server error via the Web Gui.

I do however have access via the CLI.

 

I ran the debug commands mentioned above

diagnose debug enable diag debug application httpsd -1 diagnose web-ui debug enable

 

FG100Dfirewall# [httpsd 127 - 1429256952] http_config.c[558] ap_invoke_handler -- new request (handler='index-handler', uri='/index', method='GET') [httpsd 127 - 1429256952] http_config.c[562] ap_invoke_handler -- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 [httpsd 127 - 1429256952] http_config.c[565] ap_invoke_handler -- Source: 41.189.93.126:24502 Destination: 10.200.1.201:65443 [httpsd 127 - 1429256952] http_config.c[581] ap_invoke_handler -- request completed (handler='index-handler' result==0) [httpsd 127 - 1429256952] http_config.c[558] ap_invoke_handler -- new request (handler='fastcgi-script', uri='/p/system/navbar/', method='GET') [httpsd 127 - 1429256952] http_config.c[562] ap_invoke_handler -- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 [httpsd 127 - 1429256952] http_config.c[565] ap_invoke_handler -- Source: 41.189.93.126:24502 Destination: 10.200.1.201:65443 [httpsd 483 - 1429256957] wij_navbar.c[89] get_actual_log_device -- changing from vdom 'root' to vdom 'root' [httpsd 483 - 1429256957] wij_navbar.c[114] get_actual_log_device -- log device for vdom 'root' is '1' [httpsd 483 - 1429256957] wij_navbar.c[116] get_actual_log_device -- returning to original vdom 'root' lock_crash(): Can't lock [httpsd 127 - 1429256987] http_log.c[439] log_error_core -- [Fri Apr 17 09:49:47 2015] [error] [client 41.189.93.126] FastCGI: comm with server "/migadmin/index.py" aborted: idle timeout (30 sec) [httpsd 127 - 1429256987] http_log.c[439] log_error_core -- [Fri Apr 17 09:49:47 2015] [error] [client 41.189.93.126] FastCGI: incomplete headers (0 bytes) received from server "/migadmin/index.py" [httpsd 127 - 1429256987] http_config.c[581] ap_invoke_handler -- request completed (handler='fastcgi-script' result==500) [httpsd 127 - 1429256987] http_request.c[1443] ap_internal_redirect -- internal redirect to '/p/pubredir/httperror/' [httpsd 127 - 1429256987] http_config.c[558] ap_invoke_handler -- new request (handler='fastcgi-script', uri='/p/pubredir/httperror/', method='GET') [httpsd 127 - 1429256987] http_config.c[562] ap_invoke_handler -- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 [httpsd 127 - 1429256987] http_config.c[565] ap_invoke_handler -- Source: 41.189.93.126:24502 Destination: 10.200.1.201:65443 [httpsd 127 - 1429256987] http_config.c[581] ap_invoke_handler -- request completed (handler='fastcgi-script' result==0) [httpsd 150 - 1429256987] http_config.c[558] ap_invoke_handler -- new request (handler='api_cmdb-handler', uri='/api/cmdb?request=%7B%22action%22%3A%22select%22%2C%22path%22%3A%22system%22%2C%22name%22%3A%22settings%22%2C%22format%22%3A%7B%22opmode%22%3A%22%25opmode%22%7D%7D', method='GET') [httpsd 150 - 1429256987] http_config.c[562] ap_invoke_handler -- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 [httpsd 150 - 1429256987] http_config.c[565] ap_invoke_handler -- Source: 41.189.93.126:24514 Destination: 10.200.1.201:65443 [httpsd 150 - 1429256987] jsonrpc_cmdb.c[774] api_cmdb_select_etag -- ETag check for root.system.settings [httpsd 150 - 1429256987] jsonrpc_cmdb.c[787] api_cmdb_select_etag -- ETag match: 1#0 [httpsd 150 - 1429256987] http_config.c[581] ap_invoke_handler -- request completed (handler='api_cmdb-handler' result==304)

FCNSA FortiGate 60C, 110C, 200B, 310B FortiAnalyzer 100C FortiMail 100 FortiManager 100
FCNSA FortiGate 60C, 110C, 200B, 310B FortiAnalyzer 100C FortiMail 100 FortiManager 100
Christopher_McMullan

What firmware version are you running, CorneJvV?

 

Could you post the output here from 'get sys stat'?

Regards, Chris McMullan Fortinet Ottawa

CorneJvV
New Contributor

Sorry for the delayed reply.

When I am logged in on the FortiGate I have an "Error 500: Internal Server Error" on my left hand side screen.

 

Version: FortiGate-100D v5.2.1,build0618,140915 (GA) Virus-DB: 25.00409(2015-04-20 15:14) Extended DB: 1.00000(2012-10-17 15:46) IPS-DB: 6.00635(2015-04-16 02:42) IPS-ETDB: 0.00000(2001-01-01 00:00) Botnet DB: 1.00000(2012-05-28 22:51) BIOS version: 05000006 System Part-Number: P11510-04 Log hard disk: Available Internal Switch mode: interface Hostname: FG100DFirewall Operation Mode: NAT Current virtual domain: root Max number of virtual domains: 10 Virtual domains status: 1 in NAT mode, 0 in TP mode Virtual domain configuration: disable FIPS-CC mode: disable Current HA mode: standalone Branch point: 618 Release Version Information: GA FortiOS x86-64: Yes System time: Tue Apr 21 07:06:55 2015

FCNSA FortiGate 60C, 110C, 200B, 310B FortiAnalyzer 100C FortiMail 100 FortiManager 100
FCNSA FortiGate 60C, 110C, 200B, 310B FortiAnalyzer 100C FortiMail 100 FortiManager 100
Labels
Top Kudoed Authors