FortiManager GUI Not Accessible inspite of being able to ping it

[royarpit]

Hi Experts,

I'm trying to setup a Virtual FortiManager on my EVE-NG platform. I have performed the following configurations on it through the CLI:

config system interface     edit "port2"         set ip 192.168.1.200 255.255.255.0         set allowaccess ping https ssh http     next end

My workstation IP is 192.168.1.14 and I'm am able to ping it successfully.

C:\Users\Arpit>ping 192.168.1.200 Pinging 192.168.1.200 with 32 bytes of data: Reply from 192.168.1.200: bytes=32 time=119ms TTL=64 Reply from 192.168.1.200: bytes=32 time=211ms TTL=64 Reply from 192.168.1.200: bytes=32 time=307ms TTL=64 Reply from 192.168.1.200: bytes=32 time=389ms TTL=64 Ping statistics for 192.168.1.200:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 119ms, Maximum = 389ms, Average = 256ms

However, whenever I try to access the FortiManager WebGUI on a browser (Chrome, FireFox, etc.) I receive the following error:

This site can’t be reached

192.168.1.200 refused to connect.

If someone is aware of this problem, kindly let me know how I could rectify this to access the FMG WebGUI.

Any help would be greatly appreciated :)

Regards,

Arpit Roy

[Iraj]

I had the same problem, Just increased the RAM to 4GB (4096)

[wilson-2022]

 as far as i know, you can try to add the memory from default 1024 to 4096. i resovled the same problem. webservice should be enabled under the management port. my fortimanager version is v7.2.0-build1124 220411 (GA)

[wpaz]

 I had the same problem, and resolve increase the memory to 8192 and 4 cpu.

Before that the fortimanager was try to create the LVM but does not work, and after increase the memory and cpu, works as expected.

[Keilon]

This work for me.

[Battal]

After increased the memory ii didn't work, but after increased the memory and CPU it works 

[ede_pfau]

In case you try to connect from a different subnet, you need to install a default route first:

conf sys route

edit 0

set dstint port1

set dest 0.0.0.0/0

set gateway x.x.x.x

next

end

(from memory, you'll find the exact syntax, it's similar to FortiOS).

Of course, this is not the root cause if your PC is on the same subnet. A valid ping test will show you that a route is not needed.

And, for "trusted hosts", these are not preset in a new VM.

[Ghofrane35]

i have problem who can help me 

i can't ping to the @OF fortinet from cmd also i Can't ping to 8.8.8.8 and the GUI is not connect  neeeeed help plzzz

[Iraj]

Just increase the RAM to 4BG (4096).

good luck

[sw2090]

just as a tip: ping is kernel based while http(s) is a service.

So ping may work but http(s) may not.

In this case you coud try to debug it on cli with somethng like

dia debug enable

dia debug app httpd/httpsd 

this will give you some debug log output that might give you a clue on what is  wrong.